bridge1: port 1(bridge_slave_0) entered disabled state device bridge_slave_0 entered promiscuous mode bridge1: port 1(bridge_slave_0) entered blocking state bridge1: port 1(bridge_slave_0) entered forwarding state ====================================================== WARNING: possible circular locking dependency detected 4.19.124-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/14852 is trying to acquire lock: 000000000749e051 (&ovl_i_mutex_dir_key[depth]#2){++++}, at: inode_lock_shared include/linux/fs.h:758 [inline] 000000000749e051 (&ovl_i_mutex_dir_key[depth]#2){++++}, at: lookup_slow+0x43/0x70 fs/namei.c:1688 but task is already holding lock: 00000000ea64f815 (&sig->cred_guard_mutex){+.+.}, at: prepare_bprm_creds+0x51/0x120 fs/exec.c:1406 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&sig->cred_guard_mutex){+.+.}: lock_trace+0x45/0xe0 fs/proc/base.c:402 proc_pid_stack+0x12c/0x290 fs/proc/base.c:452 proc_single_show+0xeb/0x170 fs/proc/base.c:755 seq_read+0x4b9/0x10c0 fs/seq_file.c:229 do_loop_readv_writev fs/read_write.c:701 [inline] do_loop_readv_writev fs/read_write.c:688 [inline] do_iter_read+0x46b/0x640 fs/read_write.c:925 SELinux: unrecognized netlink message: protocol=0 nlmsg_type=65535 sclass=netlink_route_socket pid=14859 comm=syz-executor.2 vfs_readv+0xf0/0x160 fs/read_write.c:987 do_preadv+0x1b6/0x270 fs/read_write.c:1071 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #2 (&p->lock){+.+.}: seq_read+0x6b/0x10c0 fs/seq_file.c:161 proc_reg_read+0x1bd/0x280 fs/proc/inode.c:231 do_loop_readv_writev fs/read_write.c:701 [inline] do_loop_readv_writev fs/read_write.c:688 [inline] do_iter_read+0x46b/0x640 fs/read_write.c:925 vfs_readv+0xf0/0x160 fs/read_write.c:987 kernel_readv fs/splice.c:362 [inline] default_file_splice_read+0x477/0x970 fs/splice.c:417 do_splice_to+0x10e/0x160 fs/splice.c:881 splice_direct_to_actor+0x2b9/0x8d0 fs/splice.c:959 do_splice_direct+0x1a8/0x270 fs/splice.c:1068 do_sendfile+0x549/0xc10 fs/read_write.c:1447 __do_sys_sendfile64 fs/read_write.c:1508 [inline] __se_sys_sendfile64+0x147/0x160 fs/read_write.c:1494 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (sb_writers#3){.+.+}: sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_do_remove+0xf8/0xd70 fs/overlayfs/dir.c:843 vfs_rmdir fs/namei.c:3882 [inline] vfs_rmdir+0x18b/0x450 fs/namei.c:3861 do_rmdir+0x371/0x3e0 fs/namei.c:3943 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&ovl_i_mutex_dir_key[depth]#2){++++}: down_read+0x37/0xb0 kernel/locking/rwsem.c:24 inode_lock_shared include/linux/fs.h:758 [inline] lookup_slow+0x43/0x70 fs/namei.c:1688 walk_component+0x759/0xd30 fs/namei.c:1811 link_path_walk.part.0+0x906/0x1220 fs/namei.c:2142 link_path_walk fs/namei.c:2073 [inline] path_openat+0x1e7/0x2eb0 fs/namei.c:3536 do_filp_open+0x1a1/0x280 fs/namei.c:3567 do_open_execat+0x124/0x5b0 fs/exec.c:853 __do_execve_file.isra.0+0x18d6/0x20c0 fs/exec.c:1757 do_execveat_common fs/exec.c:1866 [inline] do_execve+0x2e/0x40 fs/exec.c:1883 __do_sys_execve fs/exec.c:1964 [inline] __se_sys_execve fs/exec.c:1959 [inline] __x64_sys_execve+0x7c/0xa0 fs/exec.c:1959 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Chain exists of: &ovl_i_mutex_dir_key[depth]#2 --> &p->lock --> &sig->cred_guard_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sig->cred_guard_mutex); lock(&p->lock); lock(&sig->cred_guard_mutex); lock(&ovl_i_mutex_dir_key[depth]#2); *** DEADLOCK *** 1 lock held by syz-executor.1/14852: #0: 00000000ea64f815 (&sig->cred_guard_mutex){+.+.}, at: prepare_bprm_creds+0x51/0x120 fs/exec.c:1406 stack backtrace: CPU: 1 PID: 14852 Comm: syz-executor.1 Not tainted 4.19.124-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+0x1fc/0x2fe lib/dump_stack.c:118 print_circular_bug.isra.0.cold+0x2dc/0x425 kernel/locking/lockdep.c:1221 check_prev_add kernel/locking/lockdep.c:1865 [inline] check_prevs_add kernel/locking/lockdep.c:1978 [inline] validate_chain kernel/locking/lockdep.c:2419 [inline] __lock_acquire+0x3145/0x4380 kernel/locking/lockdep.c:3415 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907 down_read+0x37/0xb0 kernel/locking/rwsem.c:24 inode_lock_shared include/linux/fs.h:758 [inline] lookup_slow+0x43/0x70 fs/namei.c:1688 walk_component+0x759/0xd30 fs/namei.c:1811 link_path_walk.part.0+0x906/0x1220 fs/namei.c:2142 link_path_walk fs/namei.c:2073 [inline] path_openat+0x1e7/0x2eb0 fs/namei.c:3536 do_filp_open+0x1a1/0x280 fs/namei.c:3567 do_open_execat+0x124/0x5b0 fs/exec.c:853 __do_execve_file.isra.0+0x18d6/0x20c0 fs/exec.c:1757 do_execveat_common fs/exec.c:1866 [inline] do_execve+0x2e/0x40 fs/exec.c:1883 __do_sys_execve fs/exec.c:1964 [inline] __se_sys_execve fs/exec.c:1959 [inline] __x64_sys_execve+0x7c/0xa0 fs/exec.c:1959 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x45ca29 Code: 0d b7 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 db b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007f90e7e4cc78 EFLAGS: 00000246 ORIG_RAX: 000000000000003b RAX: ffffffffffffffda RBX: 00000000004db840 RCX: 000000000045ca29 RDX: 0000000020001e40 RSI: 0000000020000540 RDI: 00000000200001c0 RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff R13: 00000000000000a8 R14: 00000000004c35ac R15: 00007f90e7e4d6d4 SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14843 comm=syz-executor.5 overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. SELinux: unrecognized netlink message: protocol=0 nlmsg_type=57 sclass=netlink_route_socket pid=14858 comm=syz-executor.2 overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 overlayfs: unrecognized mount option "wo˜°diŽ=./file5" or missing value overlayfs: unrecognized mount option "wo˜°diŽ=./file5" or missing value overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: failed to resolve './file0': -2 overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 overlayfs: unrecognized mount option "workd`w=./file1" or missing value overlayfs: unrecognized mount option "workd`w=./file1" or missing value overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 overlayfs: unrecognized mount option "lrkdir=./file1" or missing value overlayfs: unrecognized mount option "lrkdir=./file1" or missing value overlayfs: failed to resolve './file0': -2 overlayfs: at least 2 lowerdir are needed while upperdir nonexistent overlayfs: at least 2 lowerdir are needed while upperdir nonexistent overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 overlayfs: unrecognized mount option "lowerfir=./bus" or missing value overlayfs: unrecognized mount option "ÞÝ" or missing value overlayfs: unrecognized mount option "ÞÝ" or missing value overlayfs: failed to resolve './file0Oz‰ÙöË.': -2 overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0Oz‰ÙöË.': -2 overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: failed to resolve './file0': -2 overlayfs: filesystem on './file0' not supported as upperdir overlayfs: failed to resolve './file0': -2 overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: unrecognized mount option "lowerd)r=./bus" or missing value overlayfs: filesystem on './file0' not supported as upperdir overlayfs: unrecognized mount option "lowerd)r=./bus" or missing value overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: filesystem on './file0' not supported as upperdir overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=15129 comm=syz-executor.1 overlayfs: unrecognized mount option "^okdir9./file1" or missing value SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=15129 comm=syz-executor.1 overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: filesystem on './file0' not supported as upperdir overlayfs: failed to resolve './file1': -2 overlayfs: filesystem on './file0' not supported as upperdir overlayfs: failed to resolve './file1': -2 overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: filesystem on './file0' not supported as upperdir SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=15235 comm=syz-executor.2 overlayfs: unrecognized mount option "^okdir9./file1" or missing value SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=15261 comm=syz-executor.2 overlayfs: filesystem on './file0' not supported as upperdir overlayfs: unrecognized mount option "^okdir9./file1" or missing value SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=15291 comm=syz-executor.2 overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: filesystem on './file0' not supported as upperdir SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=15314 comm=syz-executor.2 overlayfs: option "workdir=./file1r=./file0" is useless in a non-upper mount, ignore overlayfs: at least 2 lowerdir are needed while upperdir nonexistent overlayfs: option "workdir=./file1r=./file0" is useless in a non-upper mount, ignore overlayfs: at least 2 lowerdir are needed while upperdir nonexistent overlayfs: unrecognized mount option "^okdir9./file1" or missing value SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=15345 comm=syz-executor.2 overlayfs: filesystem on './file0' not supported as upperdir overlayfs: unrecognized mount option "^okdir9./file1" or missing value SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=15368 comm=syz-executor.2 overlayfs: filesystem on './file0' not supported as upperdir overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: option "workdir=." is useless in a non-upper mount, ignore overlayfs: at least 2 lowerdir are needed while upperdir nonexistent overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: option "workdir=." is useless in a non-upper mount, ignore overlayfs: at least 2 lowerdir are needed while upperdir nonexistent overlayfs: filesystem on './file0' not supported as upperdir overlayfs: unrecognized mount option "u" or missing value overlayfs: failed to resolve './file0] =aøu': -2 overlayfs: unrecognized mount option "u" or missing value overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: failed to resolve './file0] =aøu': -2 overlayfs: unrecognized mount option "lowerQir=./bus" or missing value overlayfs: unrecognized mount option "lowerQir=./bus" or missing value overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: unrecognized mount option "lowu‚v/ÞõŠÁ¹W*L©wofile1" or missing value overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: unrecognized mount option "lowu‚v/ÞõŠÁ¹W*L©wofile1" or missing value overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: unrecognized mount option "^okdir9./file1" or missing value overlayfs: filesystem on './file0' not supported as upperdir overlayfs: unrecognized mount option "^okdir9./file1" or missing value