====================================================== WARNING: possible circular locking dependency detected 5.16.0-rc5-next-20211216-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/6348 is trying to acquire lock: ffffffff8bcaab60 (fs_reclaim){+.+.}-{0:0}, at: might_alloc include/linux/sched/mm.h:253 [inline] ffffffff8bcaab60 (fs_reclaim){+.+.}-{0:0}, at: slab_pre_alloc_hook mm/slab.h:739 [inline] ffffffff8bcaab60 (fs_reclaim){+.+.}-{0:0}, at: slab_alloc_node mm/slub.c:3145 [inline] ffffffff8bcaab60 (fs_reclaim){+.+.}-{0:0}, at: slab_alloc mm/slub.c:3239 [inline] ffffffff8bcaab60 (fs_reclaim){+.+.}-{0:0}, at: kmem_cache_alloc+0x3e/0x3a0 mm/slub.c:3244 but task is already holding lock: ffff88807e5e3058 (&mapping->i_mmap_rwsem){++++}-{3:3}, at: i_mmap_lock_read include/linux/fs.h:507 [inline] ffff88807e5e3058 (&mapping->i_mmap_rwsem){++++}-{3:3}, at: split_huge_page_to_list+0x533/0x5440 mm/huge_memory.c:2657 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&mapping->i_mmap_rwsem){++++}-{3:3}: down_write+0x90/0x150 kernel/locking/rwsem.c:1514 i_mmap_lock_write include/linux/fs.h:492 [inline] dma_resv_lockdep+0x362/0x55a drivers/dma-buf/dma-resv.c:713 do_one_initcall+0x103/0x650 init/main.c:1303 do_initcall_level init/main.c:1378 [inline] do_initcalls init/main.c:1394 [inline] do_basic_setup init/main.c:1413 [inline] kernel_init_freeable+0x6b1/0x73a init/main.c:1618 kernel_init+0x1a/0x1d0 init/main.c:1507 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 -> #0 (fs_reclaim){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3063 [inline] check_prevs_add kernel/locking/lockdep.c:3186 [inline] validate_chain kernel/locking/lockdep.c:3801 [inline] __lock_acquire+0x2a07/0x54a0 kernel/locking/lockdep.c:5027 lock_acquire kernel/locking/lockdep.c:5639 [inline] lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5604 __fs_reclaim_acquire mm/page_alloc.c:4550 [inline] fs_reclaim_acquire+0x115/0x160 mm/page_alloc.c:4564 might_alloc include/linux/sched/mm.h:253 [inline] slab_pre_alloc_hook mm/slab.h:739 [inline] slab_alloc_node mm/slub.c:3145 [inline] slab_alloc mm/slub.c:3239 [inline] kmem_cache_alloc+0x3e/0x3a0 mm/slub.c:3244 xas_split_alloc+0x142/0x480 lib/xarray.c:1017 split_huge_page_to_list+0xd35/0x5440 mm/huge_memory.c:2683 split_huge_page include/linux/huge_mm.h:192 [inline] truncate_inode_partial_folio+0xaed/0xe00 mm/truncate.c:272 shmem_undo_range+0xc43/0x19b0 mm/shmem.c:959 shmem_truncate_range mm/shmem.c:1037 [inline] shmem_setattr+0x59f/0x8f0 mm/shmem.c:1096 notify_change+0xb8c/0x12a0 fs/attr.c:410 do_truncate+0x13c/0x200 fs/open.c:65 do_sys_ftruncate+0x542/0x740 fs/open.c:193 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&mapping->i_mmap_rwsem); lock(fs_reclaim); lock(&mapping->i_mmap_rwsem); lock(fs_reclaim); *** DEADLOCK *** 3 locks held by syz-executor.1/6348: #0: ffff888019aa8460 (sb_writers#3){.+.+}-{0:0}, at: do_syscall_x64 arch/x86/entry/common.c:50 [inline] #0: ffff888019aa8460 (sb_writers#3){.+.+}-{0:0}, at: do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 #1: ffff88807e5e2e00 (&sb->s_type->i_mutex_key#8){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:777 [inline] #1: ffff88807e5e2e00 (&sb->s_type->i_mutex_key#8){+.+.}-{3:3}, at: do_truncate+0x12a/0x200 fs/open.c:63 #2: ffff88807e5e3058 (&mapping->i_mmap_rwsem){++++}-{3:3}, at: i_mmap_lock_read include/linux/fs.h:507 [inline] #2: ffff88807e5e3058 (&mapping->i_mmap_rwsem){++++}-{3:3}, at: split_huge_page_to_list+0x533/0x5440 mm/huge_memory.c:2657 stack backtrace: CPU: 0 PID: 6348 Comm: syz-executor.1 Not tainted 5.16.0-rc5-next-20211216-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2143 check_prev_add kernel/locking/lockdep.c:3063 [inline] check_prevs_add kernel/locking/lockdep.c:3186 [inline] validate_chain kernel/locking/lockdep.c:3801 [inline] __lock_acquire+0x2a07/0x54a0 kernel/locking/lockdep.c:5027 lock_acquire kernel/locking/lockdep.c:5639 [inline] lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5604 __fs_reclaim_acquire mm/page_alloc.c:4550 [inline] fs_reclaim_acquire+0x115/0x160 mm/page_alloc.c:4564 might_alloc include/linux/sched/mm.h:253 [inline] slab_pre_alloc_hook mm/slab.h:739 [inline] slab_alloc_node mm/slub.c:3145 [inline] slab_alloc mm/slub.c:3239 [inline] kmem_cache_alloc+0x3e/0x3a0 mm/slub.c:3244 xas_split_alloc+0x142/0x480 lib/xarray.c:1017 split_huge_page_to_list+0xd35/0x5440 mm/huge_memory.c:2683 split_huge_page include/linux/huge_mm.h:192 [inline] truncate_inode_partial_folio+0xaed/0xe00 mm/truncate.c:272 shmem_undo_range+0xc43/0x19b0 mm/shmem.c:959 shmem_truncate_range mm/shmem.c:1037 [inline] shmem_setattr+0x59f/0x8f0 mm/shmem.c:1096 notify_change+0xb8c/0x12a0 fs/attr.c:410 do_truncate+0x13c/0x200 fs/open.c:65 do_sys_ftruncate+0x542/0x740 fs/open.c:193 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f1d757b5e99 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f1d7412b168 EFLAGS: 00000246 ORIG_RAX: 000000000000004d RAX: ffffffffffffffda RBX: 00007f1d758c8f60 RCX: 00007f1d757b5e99 RDX: 0000000000000000 RSI: 0000000000000546 RDI: 000000000000000b RBP: 00007f1d7580fff1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe6cbd5eff R14: 00007f1d7412b300 R15: 0000000000022000