staging: android: ashmem: Fix possible deadlock in ashmem_ioctl
authorYisheng Xie <xieyisheng1@huawei.com>
Wed, 28 Feb 2018 06:59:22 +0000 (14:59 +0800)
committerJoel Fernandes <joelaf@google.com>
Mon, 19 Mar 2018 22:11:13 +0000 (15:11 -0700)
commitfdcb8f51789a70e62c0ffab7e0f640a409ef307a
tree632aba8aead849bf5fff38ee9617e749e4d2f9f5
parent267c6efd76b774f0b14bee1d814177be06748de8
staging: android: ashmem: Fix possible deadlock in ashmem_ioctl

ashmem_mutex may create a chain of dependencies like:

CPU0                                    CPU1
 mmap syscall                           ioctl syscall
 -> mmap_sem (acquired)                 -> ashmem_ioctl
 -> ashmem_mmap                            -> ashmem_mutex (acquired)
    -> ashmem_mutex (try to acquire)       -> copy_from_user
                                              -> mmap_sem (try to acquire)

There is a lock odering problem between mmap_sem and ashmem_mutex causing
a lockdep splat[1] during a syzcaller test. This patch fixes the problem
by move copy_from_user out of ashmem_mutex.

[1] https://www.spinics.net/lists/kernel/msg2733200.html

Fixes: ce8a3a9e76d0 (staging: android: ashmem: Fix a race condition in pin ioctls)
Reported-by: syzbot+d7a918a7a8e1c952bc36@syzkaller.appspotmail.com
Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/android/ashmem.c