bond1: now running without any active interface! vhci_hcd: stop threads vhci_hcd: release socket vhci_hcd: disconnect device ====================================================== WARNING: possible circular locking dependency detected 4.19.195-syzkaller #0 Not tainted ------------------------------------------------------ kworker/1:3/9098 is trying to acquire lock: 000000003ed99fad (&sb->s_type->i_mutex_key#13){+.+.}, at: inode_lock include/linux/fs.h:748 [inline] 000000003ed99fad (&sb->s_type->i_mutex_key#13){+.+.}, at: __sock_release+0x86/0x2a0 net/socket.c:578 but task is already holding lock: 00000000053ab97c ((delayed_fput_work).work){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 ((delayed_fput_work).work){+.+.}: worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 -> #2 ((wq_completion)"events"){+.+.}: flush_scheduled_work include/linux/workqueue.h:599 [inline] tipc_exit_net+0x38/0x60 net/tipc/core.c:100 ops_exit_list+0xa5/0x150 net/core/net_namespace.c:153 cleanup_net+0x3b4/0x8b0 net/core/net_namespace.c:553 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 -> #1 (pernet_ops_rwsem){++++}: unregister_netdevice_notifier+0x7b/0x330 net/core/dev.c:1708 bcm_release+0x94/0x700 net/can/bcm.c:1525 __sock_release+0xcd/0x2a0 net/socket.c:579 sock_close+0x15/0x20 net/socket.c:1140 __fput+0x2ce/0x890 fs/file_table.c:278 task_work_run+0x148/0x1c0 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:193 [inline] exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167 prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline] syscall_return_slowpath arch/x86/entry/common.c:271 [inline] do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&sb->s_type->i_mutex_key#13){+.+.}: down_write+0x34/0x90 kernel/locking/rwsem.c:70 inode_lock include/linux/fs.h:748 [inline] __sock_release+0x86/0x2a0 net/socket.c:578 sock_close+0x15/0x20 net/socket.c:1140 __fput+0x2ce/0x890 fs/file_table.c:278 delayed_fput+0x56/0x70 fs/file_table.c:304 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 other info that might help us debug this: Chain exists of: &sb->s_type->i_mutex_key#13 --> (wq_completion)"events" --> (delayed_fput_work).work Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock((delayed_fput_work).work); lock((wq_completion)"events"); lock((delayed_fput_work).work); lock(&sb->s_type->i_mutex_key#13); *** DEADLOCK *** 2 locks held by kworker/1:3/9098: #0: 000000007cb5a45d ((wq_completion)"events"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124 #1: 00000000053ab97c ((delayed_fput_work).work){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128 stack backtrace: CPU: 1 PID: 9098 Comm: kworker/1:3 Not tainted 4.19.195-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events delayed_fput 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 down_write+0x34/0x90 kernel/locking/rwsem.c:70 inode_lock include/linux/fs.h:748 [inline] __sock_release+0x86/0x2a0 net/socket.c:578 sock_close+0x15/0x20 net/socket.c:1140 __fput+0x2ce/0x890 fs/file_table.c:278 delayed_fput+0x56/0x70 fs/file_table.c:304 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 ntfs: (device loop2): parse_options(): Unrecognized mount option n|s. ntfs: (device loop2): parse_options(): Unrecognized mount option n|s. overlayfs: unrecognized mount option "work;Ār=./file1" or missing value overlayfs: unrecognized mount option "work;Ār=./file1" or missing value EXT4-fs (loop2): Ignoring removed oldalloc option EXT4-fs (loop2): Ignoring removed orlov option EXT4-fs (loop2): ext4_check_descriptors: Checksum for group 0 failed (60935!=0) overlayfs: unrecognized mount option "work;Ār=./file1" or missing value EXT4-fs (loop2): orphan cleanup on readonly fs EXT4-fs error (device loop2): ext4_orphan_get:1257: comm syz-executor.2: bad orphan inode 33554432 EXT4-fs (loop2): mounted filesystem without journal. Opts: usrjquota=,oldalloc,resgid=0x0000000000000000,orlov,,errors=continue overlayfs: unrecognized mount option "work;Ār=./file1" or missing value encrypted_key: key user:syz not found encrypted_key: keyword 'new' not allowed when called from .update method overlayfs: unrecognized mount option "work;Ār=./file1" or missing value overlayfs: unrecognized mount option "work;Ār=./file1" or missing value audit: type=1804 audit(1624923992.795:133): pid=21418 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir336080579/syzkaller.IOKR5z/133/cgroup.controllers" dev="sda1" ino=14599 res=1 device wlan1 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready netlink: 'syz-executor.3': attribute type 2 has an invalid length. overlayfs: unrecognized mount option "work;Ār=./file1" or missing value device wlan1 left promiscuous mode device wlan1 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready overlayfs: unrecognized mount option "work;Ār=./file1" or missing value IPVS: ftp: loaded support on port[0] = 21 overlayfs: unrecognized mount option "work;Ār=./file1" or missing value netlink: 24 bytes leftover after parsing attributes in process `syz-executor.3'. overlayfs: unrecognized mount option "work;Ār=./file1" or missing value netlink: 8 bytes leftover after parsing attributes in process `syz-executor.3'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.3'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.3'. overlayfs: unrecognized mount option "work;Ār=./file1" or missing value IPVS: Unknown mcast interface: virt_wifk0 overlayfs: unrecognized mount option "work;Ār=./file1" or missing value IPVS: Unknown mcast interface: virt_wifk0 ip6_tunnel: ip6tnl1 xmit: Local address not yet configured! overlayfs: unrecognized mount option "work;Ār=./file1" or missing value overlayfs: unrecognized mount option "work;Ār=./file1" or missing value ubi0: attaching mtd0 ubi0: scanning is finished overlayfs: unrecognized mount option "work;Ār=./file1" or missing value netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ubi0: attached mtd0 (name "mtdram test device", size 0 MiB) ubi0: PEB size: 4096 bytes (4 KiB), LEB size: 3968 bytes ubi0: min./max. I/O unit sizes: 1/64, sub-page size 1 overlayfs: unrecognized mount option "work;Ār=./file1" or missing value ubi0: VID header offset: 64 (aligned 64), data offset: 128 ubi0: good PEBs: 32, bad PEBs: 0, corrupted PEBs: 0 ubi0: user volume: 0, internal volumes: 1, max. volumes count: 23 ubi0: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 1512285049 ubi0: available PEBs: 28, total reserved PEBs: 4, PEBs reserved for bad PEB handling: 0 ubi0: background thread "ubi_bgt0d" started, PID 21557 overlayfs: unrecognized mount option "work;Ār=./file1" or missing value ubi0: detaching mtd0 ubi0: mtd0 is detached overlayfs: unrecognized mount option "work;Ār=./file1" or missing value overlayfs: unrecognized mount option "work;Ār=./file1" or missing value ubi0: attaching mtd0 ubi0: scanning is finished netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. ubi0 error: ubi_attach_mtd_dev: cannot spawn "ubi_bgt0d", error -4 ubi0: attaching mtd0 ubi0: scanning is finished overlayfs: unrecognized mount option "work;Ār=./file1" or missing value netlink: 24 bytes leftover after parsing attributes in process `syz-executor.3'. ubi0: attached mtd0 (name "mtdram test device", size 0 MiB) netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. overlayfs: unrecognized mount option "work;Ār=./file1" or missing value ubi0: PEB size: 4096 bytes (4 KiB), LEB size: 3968 bytes ubi0: min./max. I/O unit sizes: 1/64, sub-page size 1 ubi0: VID header offset: 64 (aligned 64), data offset: 128 ubi0: good PEBs: 32, bad PEBs: 0, corrupted PEBs: 0 ubi0: user volume: 0, internal volumes: 1, max. volumes count: 23 ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1512285049 ubi0: available PEBs: 28, total reserved PEBs: 4, PEBs reserved for bad PEB handling: 0 ubi0: background thread "ubi_bgt0d" started, PID 21624 overlayfs: unrecognized mount option "work;Ār=./file1" or missing value ubi: mtd0 is already attached to ubi0 ubi0: detaching mtd0 ubi0: mtd0 is detached