wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50 IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50 IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready ====================================================== WARNING: possible circular locking dependency detected audit: type=1804 audit(1656859209.992:553): pid=22012 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.4" name="/root/syzkaller-testdir3449498643/syzkaller.ya18bE/0/bus" dev="sda1" ino=14289 res=1 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.4/22011 is trying to acquire lock: 00000000e06ddd91 (&p->lock){+.+.}, at: seq_read+0x6b/0x11c0 fs/seq_file.c:164 but task is already holding lock: 00000000d511daed (sb_writers#3){.+.+}, at: file_start_write include/linux/fs.h:2779 [inline] 00000000d511daed (sb_writers#3){.+.+}, at: do_sendfile+0x97d/0xc30 fs/read_write.c:1446 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (sb_writers#3){.+.+}: sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_do_remove+0xf0/0xdb0 fs/overlayfs/dir.c:845 vfs_rmdir.part.0+0x10f/0x3d0 fs/namei.c:3882 vfs_rmdir fs/namei.c:3868 [inline] do_rmdir+0x3fd/0x490 fs/namei.c:3943 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #2 (&ovl_i_mutex_dir_key[depth]#2){++++}: inode_lock_shared include/linux/fs.h:758 [inline] do_last fs/namei.c:3326 [inline] path_openat+0x17ec/0x2df0 fs/namei.c:3537 do_filp_open+0x18c/0x3f0 fs/namei.c:3567 do_open_execat+0x11d/0x5b0 fs/exec.c:853 __do_execve_file+0x1a8b/0x2360 fs/exec.c:1770 do_execveat_common fs/exec.c:1879 [inline] do_execve+0x35/0x50 fs/exec.c:1896 __do_sys_execve fs/exec.c:1977 [inline] __se_sys_execve fs/exec.c:1972 [inline] __x64_sys_execve+0x7c/0xa0 fs/exec.c:1972 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (&sig->cred_guard_mutex){+.+.}: do_io_accounting fs/proc/base.c:2750 [inline] proc_tgid_io_accounting+0x1cf/0x7f0 fs/proc/base.c:2799 proc_single_show+0xeb/0x170 fs/proc/base.c:755 seq_read+0x4e0/0x11c0 fs/seq_file.c:232 __vfs_read+0xf7/0x750 fs/read_write.c:416 vfs_read+0x194/0x3c0 fs/read_write.c:452 ksys_read+0x12b/0x2a0 fs/read_write.c:579 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&p->lock){+.+.}: __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 seq_read+0x6b/0x11c0 fs/seq_file.c:164 proc_reg_read+0x1bd/0x2d0 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+0x471/0x630 fs/read_write.c:925 vfs_readv+0xe5/0x150 fs/read_write.c:987 kernel_readv fs/splice.c:362 [inline] default_file_splice_read+0x457/0xa00 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+0x1a7/0x270 fs/splice.c:1068 do_sendfile+0x550/0xc30 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 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.4/22011: #0: 00000000d511daed (sb_writers#3){.+.+}, at: file_start_write include/linux/fs.h:2779 [inline] #0: 00000000d511daed (sb_writers#3){.+.+}, at: do_sendfile+0x97d/0xc30 fs/read_write.c:1446 stack backtrace: CPU: 0 PID: 22011 Comm: syz-executor.4 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/29/2022 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1222 check_prev_add kernel/locking/lockdep.c:1866 [inline] check_prevs_add kernel/locking/lockdep.c:1979 [inline] validate_chain kernel/locking/lockdep.c:2420 [inline] __lock_acquire+0x30c9/0x3ff0 kernel/locking/lockdep.c:3416 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908 __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 seq_read+0x6b/0x11c0 fs/seq_file.c:164 proc_reg_read+0x1bd/0x2d0 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+0x471/0x630 fs/read_write.c:925 vfs_readv+0xe5/0x150 fs/read_write.c:987 kernel_readv fs/splice.c:362 [inline] default_file_splice_read+0x457/0xa00 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+0x1a7/0x270 fs/splice.c:1068 do_sendfile+0x550/0xc30 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 RIP: 0033:0x7f3d23ef1109 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f3d22866168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 RAX: ffffffffffffffda RBX: 00007f3d24003f60 RCX: 00007f3d23ef1109 RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004 RBP: 00007f3d23f4b05d R08: 0000000000000000 R09: 0000000000000000 R10: 4000000000010046 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe3867195f R14: 00007f3d22866300 R15: 0000000000022000 Bluetooth: hci2: command 0x0409 tx timeout netlink: 60 bytes leftover after parsing attributes in process `syz-executor.5'. FAT-fs (loop4): invalid media value (0xd1) FAT-fs (loop4): Can't find a valid FAT filesystem bridge0: port 3(erspan0) entered blocking state bridge0: port 3(erspan0) entered disabled state device erspan0 entered promiscuous mode bridge0: port 3(erspan0) entered blocking state bridge0: port 3(erspan0) entered forwarding state FAT-fs (loop4): invalid media value (0xd1) FAT-fs (loop4): Can't find a valid FAT filesystem FAT-fs (loop4): invalid media value (0xd1) hpfs: hpfs_map_sector(): read error FAT-fs (loop4): Can't find a valid FAT filesystem BTRFS info (device loop0): setting 8 feature flag hpfs: hpfs_map_sector(): read error BTRFS info (device loop0): force lzo compression, level 0 BTRFS info (device loop0): disk space caching is enabled BTRFS info (device loop0): has skinny extents block nbd4: shutting down sockets hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error block nbd4: Device being setup by another task hpfs: hpfs_map_sector(): read error BTRFS info (device loop2): setting 8 feature flag hpfs: hpfs_map_sector(): read error BTRFS info (device loop2): force lzo compression, level 0 BTRFS info (device loop2): disk space caching is enabled BTRFS info (device loop2): has skinny extents hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error hpfs: hpfs_map_sector(): read error VFS: Can't find a Minix filesystem V1 | V2 | V3 on device loop4. netlink: 16 bytes leftover after parsing attributes in process `syz-executor.3'. Bluetooth: hci2: command 0x041b tx timeout BTRFS info (device loop2): setting 8 feature flag xt_CT: You must specify a L4 protocol and not use inversions on it BTRFS info (device loop2): force lzo compression, level 0 BTRFS info (device loop2): disk space caching is enabled BTRFS info (device loop2): has skinny extents netlink: 16 bytes leftover after parsing attributes in process `syz-executor.3'. netlink: 16 bytes leftover after parsing attributes in process `syz-executor.3'. block nbd1: Device being setup by another task block nbd1: server does not support multiple connections per device. block nbd1: Device being setup by another task block nbd1: server does not support multiple connections per device. BTRFS info (device loop2): setting 8 feature flag BTRFS info (device loop2): force lzo compression, level 0 BTRFS info (device loop2): disk space caching is enabled BTRFS info (device loop2): has skinny extents block nbd1: Device being setup by another task block nbd1: server does not support multiple connections per device. VFS: Can't find a Minix filesystem V1 | V2 | V3 on device loop4. BTRFS info (device loop2): setting 8 feature flag xt_CT: You must specify a L4 protocol and not use inversions on it BTRFS info (device loop2): force lzo compression, level 0 BTRFS info (device loop2): disk space caching is enabled BTRFS info (device loop2): has skinny extents netlink: 16 bytes leftover after parsing attributes in process `syz-executor.3'. xt_CT: You must specify a L4 protocol and not use inversions on it netlink: 16 bytes leftover after parsing attributes in process `syz-executor.3'. bridge0: port 2(bridge_slave_1) entered disabled state bridge0: port 1(bridge_slave_0) entered disabled state overlayfs: failed to resolve './file0': -2 device bridge_slave_1 left promiscuous mode bridge0: port 2(bridge_slave_1) entered disabled state device bridge_slave_0 left promiscuous mode bridge0: port 1(bridge_slave_0) entered disabled state BTRFS info (device loop2): setting 8 feature flag BTRFS info (device loop2): force lzo compression, level 0 overlayfs: failed to resolve './file0': -2 BTRFS info (device loop2): disk space caching is enabled BTRFS info (device loop2): has skinny extents Bluetooth: hci2: command 0x040f tx timeout Left network mode BTRFS info (device loop2): setting 8 feature flag BTRFS info (device loop2): force lzo compression, level 0 BTRFS info (device loop2): disk space caching is enabled overlayfs: failed to resolve './file0': -2 BTRFS warning (device ): duplicate device /dev/loop3 devid 1 generation 7 scanned by syz-executor.3 (22762) BTRFS info (device loop2): has skinny extents BTRFS warning (device ): duplicate device /dev/loop3 devid 1 generation 7 scanned by syz-executor.3 (22792) BTRFS warning (device ): duplicate device /dev/loop3 devid 1 generation 7 scanned by systemd-udevd (22802) BTRFS warning (device ): duplicate device /dev/loop3 devid 1 generation 7 scanned by syz-executor.3 (22806) BTRFS warning (device ): duplicate device /dev/loop3 devid 1 generation 7 scanned by systemd-udevd (22802) BTRFS info (device loop2): setting 8 feature flag BTRFS info (device loop2): force lzo compression, level 0 BTRFS info (device loop2): disk space caching is enabled BTRFS info (device loop2): has skinny extents Process accounting resumed overlayfs: failed to resolve './file1': -2 BTRFS info (device loop2): setting 8 feature flag BTRFS info (device loop2): force lzo compression, level 0 BTRFS info (device loop2): disk space caching is enabled BTRFS info (device loop2): has skinny extents Process accounting resumed Bluetooth: hci2: command 0x0419 tx timeout BTRFS info (device loop2): setting 8 feature flag BTRFS info (device loop2): force lzo compression, level 0 BTRFS info (device loop2): disk space caching is enabled BTRFS info (device loop2): has skinny extents IPVS: ftp: loaded support on port[0] = 21 batman_adv: batadv0: Interface deactivated: batadv_slave_0 batman_adv: batadv0: Removing interface: batadv_slave_0 batman_adv: batadv0: Interface deactivated: batadv_slave_1 batman_adv: batadv0: Removing interface: batadv_slave_1 device bridge_slave_1 left promiscuous mode bridge0: port 2(bridge_slave_1) entered disabled state device bridge_slave_0 left promiscuous mode bridge0: port 1(bridge_slave_0) entered disabled state device veth1_macvtap left promiscuous mode device veth0_macvtap left promiscuous mode device veth1_vlan left promiscuous mode device veth0_vlan left promiscuous mode