====================================================== WARNING: possible circular locking dependency detected 5.6.0-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/20038 is trying to acquire lock: ffff888091e4ece8 (&sb->s_type->i_mutex_key#16){+.+.}, at: inode_lock include/linux/fs.h:792 [inline] ffff888091e4ece8 (&sb->s_type->i_mutex_key#16){+.+.}, at: shmem_fallocate+0x15a/0xd40 mm/shmem.c:2736 but task is already holding lock: ffffffff89851be0 (fs_reclaim){+.+.}, at: fs_reclaim_acquire.part.0+0x0/0x30 include/linux/uaccess.h:173 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (fs_reclaim){+.+.}: __fs_reclaim_acquire mm/page_alloc.c:4073 [inline] fs_reclaim_acquire.part.0+0x20/0x30 mm/page_alloc.c:4084 fs_reclaim_acquire mm/page_alloc.c:4670 [inline] prepare_alloc_pages mm/page_alloc.c:4667 [inline] __alloc_pages_nodemask+0x4e0/0x820 mm/page_alloc.c:4719 alloc_pages_vma+0xd9/0x600 mm/mempolicy.c:2174 shmem_alloc_page+0xb0/0x170 mm/shmem.c:1499 shmem_alloc_and_acct_page+0x160/0x980 mm/shmem.c:1524 shmem_getpage_gfp+0x51a/0x2860 mm/shmem.c:1838 shmem_getpage mm/shmem.c:154 [inline] shmem_write_begin+0x102/0x1e0 mm/shmem.c:2488 generic_perform_write+0x20a/0x4e0 mm/filemap.c:3287 __generic_file_write_iter+0x24c/0x610 mm/filemap.c:3416 generic_file_write_iter+0x3f0/0x62d mm/filemap.c:3448 call_write_iter include/linux/fs.h:1902 [inline] new_sync_write+0x49c/0x700 fs/read_write.c:483 __vfs_write+0xc9/0x100 fs/read_write.c:496 vfs_write+0x262/0x5c0 fs/read_write.c:558 ksys_write+0x127/0x250 fs/read_write.c:611 do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:294 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&sb->s_type->i_mutex_key#16){+.+.}: check_prev_add kernel/locking/lockdep.c:2475 [inline] check_prevs_add kernel/locking/lockdep.c:2580 [inline] validate_chain kernel/locking/lockdep.c:2970 [inline] __lock_acquire+0x201b/0x3ca0 kernel/locking/lockdep.c:3954 lock_acquire+0x197/0x420 kernel/locking/lockdep.c:4484 down_write+0x8d/0x150 kernel/locking/rwsem.c:1534 inode_lock include/linux/fs.h:792 [inline] shmem_fallocate+0x15a/0xd40 mm/shmem.c:2736 ashmem_shrink_scan drivers/staging/android/ashmem.c:490 [inline] ashmem_shrink_scan+0x34d/0x500 drivers/staging/android/ashmem.c:465 do_shrink_slab+0x3fc/0xab0 mm/vmscan.c:512 shrink_slab mm/vmscan.c:673 [inline] shrink_slab+0x16f/0x5f0 mm/vmscan.c:646 shrink_node_memcgs mm/vmscan.c:2676 [inline] shrink_node+0x477/0x1b20 mm/vmscan.c:2780 shrink_zones mm/vmscan.c:2983 [inline] do_try_to_free_pages+0x38d/0x13a0 mm/vmscan.c:3036 try_to_free_pages+0x293/0x8d0 mm/vmscan.c:3275 __perform_reclaim mm/page_alloc.c:4113 [inline] __alloc_pages_direct_reclaim mm/page_alloc.c:4134 [inline] __alloc_pages_slowpath+0x919/0x26a0 mm/page_alloc.c:4537 __alloc_pages_nodemask+0x5e1/0x820 mm/page_alloc.c:4751 alloc_pages_current+0xff/0x200 mm/mempolicy.c:2211 alloc_pages include/linux/gfp.h:532 [inline] ion_page_pool_alloc_pages drivers/staging/android/ion/ion_page_pool.c:19 [inline] ion_page_pool_alloc+0x186/0x280 drivers/staging/android/ion/ion_page_pool.c:78 alloc_buffer_page drivers/staging/android/ion/ion_system_heap.c:53 [inline] alloc_largest_available drivers/staging/android/ion/ion_system_heap.c:87 [inline] ion_system_heap_allocate+0x321/0xb00 drivers/staging/android/ion/ion_system_heap.c:118 ion_buffer_create drivers/staging/android/ion/ion.c:50 [inline] ion_alloc drivers/staging/android/ion/ion.c:369 [inline] ion_ioctl+0x37a/0xca0 drivers/staging/android/ion/ion.c:495 vfs_ioctl fs/ioctl.c:47 [inline] ksys_ioctl+0x11a/0x180 fs/ioctl.c:763 __do_sys_ioctl fs/ioctl.c:772 [inline] __se_sys_ioctl fs/ioctl.c:770 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:770 do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:294 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(fs_reclaim); lock(&sb->s_type->i_mutex_key#16); lock(fs_reclaim); lock(&sb->s_type->i_mutex_key#16); *** DEADLOCK *** 3 locks held by syz-executor.5/20038: #0: ffff88821a8782b8 (&idev->lock){++++}, at: ion_alloc drivers/staging/android/ion/ion.c:364 [inline] #0: ffff88821a8782b8 (&idev->lock){++++}, at: ion_ioctl+0x1ed/0xca0 drivers/staging/android/ion/ion.c:495 #1: ffffffff89851be0 (fs_reclaim){+.+.}, at: fs_reclaim_acquire.part.0+0x0/0x30 include/linux/uaccess.h:173 #2: ffffffff8982d288 (shrinker_rwsem){++++}, at: shrink_slab mm/vmscan.c:663 [inline] #2: ffffffff8982d288 (shrinker_rwsem){++++}, at: shrink_slab+0xc7/0x5f0 mm/vmscan.c:646 stack backtrace: CPU: 1 PID: 20038 Comm: syz-executor.5 Not tainted 5.6.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x188/0x20d lib/dump_stack.c:118 check_noncircular+0x32e/0x3e0 kernel/locking/lockdep.c:1808 check_prev_add kernel/locking/lockdep.c:2475 [inline] check_prevs_add kernel/locking/lockdep.c:2580 [inline] validate_chain kernel/locking/lockdep.c:2970 [inline] __lock_acquire+0x201b/0x3ca0 kernel/locking/lockdep.c:3954 lock_acquire+0x197/0x420 kernel/locking/lockdep.c:4484 down_write+0x8d/0x150 kernel/locking/rwsem.c:1534 inode_lock include/linux/fs.h:792 [inline] shmem_fallocate+0x15a/0xd40 mm/shmem.c:2736 ashmem_shrink_scan drivers/staging/android/ashmem.c:490 [inline] ashmem_shrink_scan+0x34d/0x500 drivers/staging/android/ashmem.c:465 do_shrink_slab+0x3fc/0xab0 mm/vmscan.c:512 shrink_slab mm/vmscan.c:673 [inline] shrink_slab+0x16f/0x5f0 mm/vmscan.c:646 shrink_node_memcgs mm/vmscan.c:2676 [inline] shrink_node+0x477/0x1b20 mm/vmscan.c:2780 shrink_zones mm/vmscan.c:2983 [inline] do_try_to_free_pages+0x38d/0x13a0 mm/vmscan.c:3036 try_to_free_pages+0x293/0x8d0 mm/vmscan.c:3275 __perform_reclaim mm/page_alloc.c:4113 [inline] __alloc_pages_direct_reclaim mm/page_alloc.c:4134 [inline] __alloc_pages_slowpath+0x919/0x26a0 mm/page_alloc.c:4537 __alloc_pages_nodemask+0x5e1/0x820 mm/page_alloc.c:4751 alloc_pages_current+0xff/0x200 mm/mempolicy.c:2211 alloc_pages include/linux/gfp.h:532 [inline] ion_page_pool_alloc_pages drivers/staging/android/ion/ion_page_pool.c:19 [inline] ion_page_pool_alloc+0x186/0x280 drivers/staging/android/ion/ion_page_pool.c:78 alloc_buffer_page drivers/staging/android/ion/ion_system_heap.c:53 [inline] alloc_largest_available drivers/staging/android/ion/ion_system_heap.c:87 [inline] ion_system_heap_allocate+0x321/0xb00 drivers/staging/android/ion/ion_system_heap.c:118 ion_buffer_create drivers/staging/android/ion/ion.c:50 [inline] ion_alloc drivers/staging/android/ion/ion.c:369 [inline] ion_ioctl+0x37a/0xca0 drivers/staging/android/ion/ion.c:495 vfs_ioctl fs/ioctl.c:47 [inline] ksys_ioctl+0x11a/0x180 fs/ioctl.c:763 __do_sys_ioctl fs/ioctl.c:772 [inline] __se_sys_ioctl fs/ioctl.c:770 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:770 do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:294 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x45c849 Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007f83c3784c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f83c37856d4 RCX: 000000000045c849 RDX: 0000000020000000 RSI: 00000000c0184900 RDI: 0000000000000006 RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff R13: 0000000000000364 R14: 00000000004c5d48 R15: 000000000076bf0c