====================================================== WARNING: possible circular locking dependency detected 4.14.175-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.3/2938 is trying to acquire lock: (&p->lock){+.+.}, at: [] seq_read+0xba/0x1160 fs/seq_file.c:165 but task is already holding lock: (sb_writers#3){.+.+}, at: [] file_start_write include/linux/fs.h:2708 [inline] (sb_writers#3){.+.+}, at: [] do_sendfile+0x865/0xaf0 fs/read_write.c:1440 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (sb_writers#3){.+.+}: percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] percpu_down_read include/linux/percpu-rwsem.h:59 [inline] __sb_start_write+0x1a1/0x2e0 fs/super.c:1363 sb_start_write include/linux/fs.h:1549 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 ovl_do_remove+0x65/0xb10 fs/overlayfs/dir.c:759 vfs_rmdir fs/namei.c:3908 [inline] vfs_rmdir+0x212/0x410 fs/namei.c:3886 do_rmdir+0x2d1/0x340 fs/namei.c:3968 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 -> #2 (&ovl_i_mutex_dir_key[depth]#2){++++}: down_read+0x37/0xa0 kernel/locking/rwsem.c:24 inode_lock_shared include/linux/fs.h:729 [inline] do_last fs/namei.c:3333 [inline] path_openat+0x185a/0x3c50 fs/namei.c:3569 do_filp_open+0x18e/0x250 fs/namei.c:3603 do_open_execat+0xda/0x430 fs/exec.c:849 do_execveat_common.isra.0+0x694/0x1c70 fs/exec.c:1740 do_execve fs/exec.c:1847 [inline] SYSC_execve fs/exec.c:1928 [inline] SyS_execve+0x34/0x40 fs/exec.c:1923 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 -> #1 (&sig->cred_guard_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893 lock_trace+0x3f/0xc0 fs/proc/base.c:407 proc_pid_syscall+0x81/0x1f0 fs/proc/base.c:639 proc_single_show+0xe7/0x150 fs/proc/base.c:761 seq_read+0x4d2/0x1160 fs/seq_file.c:237 do_loop_readv_writev fs/read_write.c:695 [inline] do_loop_readv_writev fs/read_write.c:682 [inline] do_iter_read+0x3e3/0x5a0 fs/read_write.c:919 vfs_readv+0xd3/0x130 fs/read_write.c:981 kernel_readv fs/splice.c:361 [inline] default_file_splice_read+0x41d/0x870 fs/splice.c:416 do_splice_to+0xfb/0x150 fs/splice.c:880 splice_direct_to_actor+0x20a/0x730 fs/splice.c:952 do_splice_direct+0x164/0x210 fs/splice.c:1061 do_sendfile+0x469/0xaf0 fs/read_write.c:1441 SYSC_sendfile64 fs/read_write.c:1502 [inline] SyS_sendfile64+0xff/0x110 fs/read_write.c:1488 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 -> #0 (&p->lock){+.+.}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3994 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893 seq_read+0xba/0x1160 fs/seq_file.c:165 proc_reg_read+0xf2/0x160 fs/proc/inode.c:217 do_loop_readv_writev fs/read_write.c:695 [inline] do_loop_readv_writev fs/read_write.c:682 [inline] do_iter_read+0x3e3/0x5a0 fs/read_write.c:919 vfs_readv+0xd3/0x130 fs/read_write.c:981 kernel_readv fs/splice.c:361 [inline] default_file_splice_read+0x41d/0x870 fs/splice.c:416 do_splice_to+0xfb/0x150 fs/splice.c:880 splice_direct_to_actor+0x20a/0x730 fs/splice.c:952 do_splice_direct+0x164/0x210 fs/splice.c:1061 do_sendfile+0x469/0xaf0 fs/read_write.c:1441 SYSC_sendfile64 fs/read_write.c:1502 [inline] SyS_sendfile64+0xff/0x110 fs/read_write.c:1488 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 other info that might help us debug this: Chain exists of: &p->lock --> &ovl_i_mutex_dir_key[depth]#2 --> sb_writers#3 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#3); lock(&ovl_i_mutex_dir_key[depth]#2); lock(sb_writers#3); lock(&p->lock); *** DEADLOCK *** 1 lock held by syz-executor.3/2938: #0: (sb_writers#3){.+.+}, at: [] file_start_write include/linux/fs.h:2708 [inline] #0: (sb_writers#3){.+.+}, at: [] do_sendfile+0x865/0xaf0 fs/read_write.c:1440 stack backtrace: CPU: 1 PID: 2938 Comm: syz-executor.3 Not tainted 4.14.175-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x13e/0x194 lib/dump_stack.c:58 print_circular_bug.isra.0.cold+0x1c4/0x282 kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1901 [inline] check_prevs_add kernel/locking/lockdep.c:2018 [inline] validate_chain kernel/locking/lockdep.c:2460 [inline] __lock_acquire+0x2cb3/0x4620 kernel/locking/lockdep.c:3487 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3994 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893 seq_read+0xba/0x1160 fs/seq_file.c:165 proc_reg_read+0xf2/0x160 fs/proc/inode.c:217 do_loop_readv_writev fs/read_write.c:695 [inline] do_loop_readv_writev fs/read_write.c:682 [inline] do_iter_read+0x3e3/0x5a0 fs/read_write.c:919 vfs_readv+0xd3/0x130 fs/read_write.c:981 kernel_readv fs/splice.c:361 [inline] default_file_splice_read+0x41d/0x870 fs/splice.c:416 do_splice_to+0xfb/0x150 fs/splice.c:880 splice_direct_to_actor+0x20a/0x730 fs/splice.c:952 do_splice_direct+0x164/0x210 fs/splice.c:1061 do_sendfile+0x469/0xaf0 fs/read_write.c:1441 SYSC_sendfile64 fs/read_write.c:1502 [inline] SyS_sendfile64+0xff/0x110 fs/read_write.c:1488 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 RIP: 0033:0x45c889 RSP: 002b:00007fb1d1a6bc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 RAX: ffffffffffffffda RBX: 00007fb1d1a6c6d4 RCX: 000000000045c889 RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004 RBP: 000000000076bf00 R08: 0000000000000000 R09: 0000000000000000 R10: 4000000000010046 R11: 0000000000000246 R12: 00000000ffffffff R13: 00000000000008d4 R14: 00000000004cb7c6 R15: 000000000076bf0c overlayfs: workdir and upperdir must be separate subtrees SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=2965 comm=syz-executor.2 hid-generic 0000:0000:0000.0003: ignoring exceeding usage max overlayfs: workdir and upperdir must be separate subtrees hid-generic 0000:0000:0000.0003: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: workdir and upperdir must be separate subtrees hid-generic 0000:0000:0000.0004: ignoring exceeding usage max hid-generic 0000:0000:0000.0004: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './fil': -2 hid-generic 0000:0000:0000.0005: ignoring exceeding usage max hid-generic 0000:0000:0000.0005: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: workdir and upperdir must be separate subtrees overlayfs: failed to resolve './fil': -2 hid-generic 0000:0000:0000.0006: ignoring exceeding usage max hid-generic 0000:0000:0000.0006: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './fil': -2 overlayfs: workdir and upperdir must be separate subtrees hid-generic 0000:0000:0000.0007: ignoring exceeding usage max hid-generic 0000:0000:0000.0007: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file': -2 overlayfs: failed to resolve './fil': -2 overlayfs: workdir and upperdir must be separate subtrees hid-generic 0000:0000:0000.0008: ignoring exceeding usage max hid-generic 0000:0000:0000.0008: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.0009: ignoring exceeding usage max overlayfs: failed to resolve './file': -2 hid-generic 0000:0000:0000.0009: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.000A: ignoring exceeding usage max overlayfs: failed to resolve './file': -2 hid-generic 0000:0000:0000.000A: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.000B: ignoring exceeding usage max hid-generic 0000:0000:0000.000B: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.000C: ignoring exceeding usage max hid-generic 0000:0000:0000.000D: ignoring exceeding usage max hid-generic 0000:0000:0000.000C: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.000D: hidraw1: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.000E: ignoring exceeding usage max hid-generic 0000:0000:0000.000E: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.000F: ignoring exceeding usage max overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.000F: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.0010: ignoring exceeding usage max hid-generic 0000:0000:0000.0010: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0011: ignoring exceeding usage max overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0011: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0012: ignoring exceeding usage max hid-generic 0000:0000:0000.0012: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0013: ignoring exceeding usage max hid-generic 0000:0000:0000.0013: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.0014: ignoring exceeding usage max overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0014: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.0015: ignoring exceeding usage max overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0015: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.0016: ignoring exceeding usage max overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0016: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.0017: ignoring exceeding usage max hid-generic 0000:0000:0000.0017: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.0018: ignoring exceeding usage max overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0018: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.0019: ignoring exceeding usage max hid-generic 0000:0000:0000.0019: hidraw0: HID v0.00 Device [syz1] on %z5 overlayfs: failed to resolve './file1': -2 hid-generic 0000:0000:0000.001A: ignoring exceeding usage max hid-generic 0000:0000:0000.001A: hidraw0: HID v0.00 Device [syz1] on %z5 hid-generic 0000:0000:0000.001B: ignoring exceeding usage max hid-generic 0000:0000:0000.001B: hidraw0: HID v0.00 Device [syz1] on %z5