overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. 8021q: adding VLAN 0 to HW filter on device batadv11 bond6: Enslaving batadv11 as a backup interface with an up link ====================================================== WARNING: possible circular locking dependency detected 4.14.307-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/12686 is trying to acquire lock: (&ovl_i_mutex_dir_key[depth]#2){++++}, at: [] iterate_dir+0x387/0x5e0 fs/readdir.c:43 but task is already holding lock: net_ratelimit: 6 callbacks suppressed bond6: Warning: No 802.3ad response from the link partner for any adapters in the bond (sb_writers#3){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] (sb_writers#3){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 ( 8021q: adding VLAN 0 to HW filter on device bond6 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+0x64/0x260 fs/super.c:1342 sb_start_write include/linux/fs.h:1551 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 ovl_setattr+0x52/0x500 fs/overlayfs/inode.c:38 notify_change+0x56b/0xd10 fs/attr.c:315 chown_common+0x40b/0x4b0 fs/open.c:631 SYSC_fchownat fs/open.c:661 [inline] SyS_fchownat+0xf6/0x190 fs/open.c:641 IPv6: ADDRCONF(NETDEV_CHANGE): bond5: link becomes ready do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 -> #0 8021q: adding VLAN 0 to HW filter on device batadv12 (&ovl_i_mutex_dir_key[depth]#2){++++}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_write_killable+0x37/0xb0 kernel/locking/rwsem.c:68 bond6: Enslaving batadv12 as a backup interface with an up link iterate_dir+0x387/0x5e0 fs/readdir.c:43 ovl_dir_read fs/overlayfs/readdir.c:306 [inline] ovl_dir_read_merged+0x2c5/0x430 fs/overlayfs/readdir.c:365 ovl_check_empty_dir+0x6e/0x200 fs/overlayfs/readdir.c:870 ovl_check_empty_and_clear+0x72/0xe0 fs/overlayfs/dir.c:306 ovl_rename+0x57d/0xe50 fs/overlayfs/dir.c:959 vfs_rename+0x560/0x1820 fs/namei.c:4498 SYSC_renameat2 fs/namei.c:4646 [inline] SyS_renameat2+0x95b/0xad0 fs/namei.c:4535 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 8021q: adding VLAN 0 to HW filter on device batadv13 ---- ---- lock(sb_writers#3 bond7: Enslaving batadv13 as a backup interface with an up link ); lock(&ovl_i_mutex_dir_key[depth]#2); lock(sb_writers#3); lock(&ovl_i_mutex_dir_key[depth]#2); IPv6: ADDRCONF(NETDEV_UP): bond7: link is not ready *** DEADLOCK *** bond7: Warning: No 802.3ad response from the link partner for any adapters in the bond 6 locks held by syz-executor.1/12686: #0: (sb_writers#14){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] #0: (sb_writers#14){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 #1: (&type->s_vfs_rename_key#2){+.+.}, at: [] lock_rename+0x54/0x280 fs/namei.c:2889 #2: 8021q: adding VLAN 0 to HW filter on device bond7 (&ovl_i_mutex_dir_key[depth]/1){+.+.}, at: [] inode_lock_nested include/linux/fs.h:754 [inline] (&ovl_i_mutex_dir_key[depth]/1){+.+.}, at: [] lock_rename+0x132/0x280 fs/namei.c:2900 #3: 8021q: adding VLAN 0 to HW filter on device batadv14 (&ovl_i_mutex_dir_key[depth]/2){+.+.}, at: [] inode_lock_nested include/linux/fs.h:754 [inline] (&ovl_i_mutex_dir_key[depth]/2){+.+.}, at: [] lock_rename+0x166/0x280 fs/namei.c:2901 #4: bond7: Enslaving batadv14 as a backup interface with an up link (&ovl_i_mutex_dir_key[depth]){++++}, at: [] inode_lock include/linux/fs.h:719 [inline] (&ovl_i_mutex_dir_key[depth]){++++}, at: [] vfs_rename+0xbd8/0x1820 fs/namei.c:4472 #5: (sb_writers#3){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] #5: (sb_writers#3){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 stack backtrace: CPU: 1 PID: 12686 Comm: syz-executor.1 Not tainted 4.14.307-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1905 [inline] check_prevs_add kernel/locking/lockdep.c:2022 [inline] validate_chain kernel/locking/lockdep.c:2464 [inline] __lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_write_killable+0x37/0xb0 kernel/locking/rwsem.c:68 iterate_dir+0x387/0x5e0 fs/readdir.c:43 ovl_dir_read fs/overlayfs/readdir.c:306 [inline] ovl_dir_read_merged+0x2c5/0x430 fs/overlayfs/readdir.c:365 ovl_check_empty_dir+0x6e/0x200 fs/overlayfs/readdir.c:870 ovl_check_empty_and_clear+0x72/0xe0 fs/overlayfs/dir.c:306 ovl_rename+0x57d/0xe50 fs/overlayfs/dir.c:959 vfs_rename+0x560/0x1820 fs/namei.c:4498 SYSC_renameat2 fs/namei.c:4646 [inline] SyS_renameat2+0x95b/0xad0 fs/namei.c:4535 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 RIP: 0033:0x7f0572ad00f9 RSP: 002b:00007f0571042168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007f0572beff80 RCX: 00007f0572ad00f9 RDX: 0000000000000000 RSI: 0000000020000440 RDI: 0000000020000100 RBP: 00007f0572b2bae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc4728067f R14: 00007f0571042300 R15: 0000000000022000 bond6: Warning: No 802.3ad response from the link partner for any adapters in the bond bond7: Warning: No 802.3ad response from the link partner for any adapters in the bond IPv6: ADDRCONF(NETDEV_CHANGE): bond7: link becomes ready overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. device lo entered promiscuous mode nla_parse: 48 callbacks suppressed netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'. IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE IPv6: NLM_F_CREATE should be set when creating new route IPv6: NLM_F_CREATE should be set when creating new route IPv6: NLM_F_CREATE should be set when creating new route netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'. IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'. IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'. IPv6: RTM_NEWROUTE with no NLM_F_CREATE or NLM_F_REPLACE kauditd_printk_skb: 381 callbacks suppressed audit: type=1804 audit(1677501551.166:1076): pid=13018 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.4" name="/root/syzkaller-testdir1051435868/syzkaller.Bcmeyr/83/bus" dev="sda1" ino=13973 res=1 audit: type=1800 audit(1677501551.166:1077): pid=13018 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="bus" dev="sda1" ino=13973 res=0 audit: type=1800 audit(1677501551.256:1078): pid=13016 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="bus" dev="sda1" ino=14070 res=0 audit: type=1800 audit(1677501551.506:1079): pid=13025 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="bus" dev="sda1" ino=13876 res=0 audit: type=1800 audit(1677501551.526:1080): pid=13029 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="bus" dev="sda1" ino=14019 res=0 audit: type=1800 audit(1677501551.556:1081): pid=13036 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="bus" dev="sda1" ino=13925 res=0 audit: type=1800 audit(1677501551.886:1082): pid=13051 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="bus" dev="sda1" ino=14114 res=0 audit: type=1800 audit(1677501551.896:1083): pid=13054 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="bus" dev="sda1" ino=14348 res=0 audit: type=1804 audit(1677501552.046:1084): pid=13066 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.4" name="/root/syzkaller-testdir1051435868/syzkaller.Bcmeyr/84/bus" dev="sda1" ino=13925 res=1 audit: type=1800 audit(1677501552.046:1085): pid=13066 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="bus" dev="sda1" ino=13925 res=0