FAT-fs (loop0): Unrecognized mount option "./bus" or missing value ====================================================== WARNING: possible circular locking dependency detected 4.14.290-syzkaller #0 Not tainted ------------------------------------------------------ kworker/1:2/4315 is trying to acquire lock: (&sb->s_type->i_mutex_key#10){+.+.}, at: [] inode_lock include/linux/fs.h:719 [inline] (&sb->s_type->i_mutex_key#10){+.+.}, at: [] __generic_file_fsync+0x9e/0x190 fs/libfs.c:989 but task is already holding lock: ((&dio->complete_work)){+.+.}, at: [] process_one_work+0x6e6/0x14a0 kernel/workqueue.c:2092 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 ((&dio->complete_work)){+.+.}: process_one_work+0x736/0x14a0 kernel/workqueue.c:2093 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251 kthread+0x30d/0x420 kernel/kthread.c:232 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404 -> #1 ("dio/%s"sb->s_id){+.+.}: flush_workqueue+0xfa/0x1310 kernel/workqueue.c:2625 drain_workqueue+0x177/0x3e0 kernel/workqueue.c:2790 destroy_workqueue+0x71/0x710 kernel/workqueue.c:4116 sb_init_dio_done_wq+0x61/0x80 fs/direct-io.c:635 do_blockdev_direct_IO fs/direct-io.c:1287 [inline] __blockdev_direct_IO+0x3df1/0xdcb0 fs/direct-io.c:1423 ext4_direct_IO_write fs/ext4/inode.c:3749 [inline] ext4_direct_IO+0x888/0x1b80 fs/ext4/inode.c:3890 generic_file_direct_write+0x1df/0x420 mm/filemap.c:2958 __generic_file_write_iter+0x2a2/0x590 mm/filemap.c:3137 ext4_file_write_iter+0x276/0xd20 fs/ext4/file.c:270 call_write_iter include/linux/fs.h:1780 [inline] aio_write+0x2ed/0x560 fs/aio.c:1553 io_submit_one fs/aio.c:1641 [inline] do_io_submit+0x847/0x1570 fs/aio.c:1709 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #0 (&sb->s_type->i_mutex_key#10){+.+.}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_write+0x34/0x90 kernel/locking/rwsem.c:54 inode_lock include/linux/fs.h:719 [inline] __generic_file_fsync+0x9e/0x190 fs/libfs.c:989 ext4_sync_file+0x8ed/0x12c0 fs/ext4/fsync.c:118 vfs_fsync_range+0x103/0x260 fs/sync.c:196 generic_write_sync include/linux/fs.h:2684 [inline] dio_complete+0x561/0x8d0 fs/direct-io.c:330 process_one_work+0x793/0x14a0 kernel/workqueue.c:2117 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251 kthread+0x30d/0x420 kernel/kthread.c:232 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404 other info that might help us debug this: Chain exists of: &sb->s_type->i_mutex_key#10 --> "dio/%s"sb->s_id --> (&dio->complete_work) Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock((&dio->complete_work)); lock("dio/%s"sb->s_id); lock((&dio->complete_work)); lock(&sb->s_type->i_mutex_key#10); *** DEADLOCK *** 2 locks held by kworker/1:2/4315: #0: ("dio/%s"sb->s_id){+.+.}, at: [] process_one_work+0x6b0/0x14a0 kernel/workqueue.c:2088 #1: ((&dio->complete_work)){+.+.}, at: [] process_one_work+0x6e6/0x14a0 kernel/workqueue.c:2092 stack backtrace: CPU: 1 PID: 4315 Comm: kworker/1:2 Not tainted 4.14.290-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022 Workqueue: dio/sda1 dio_aio_complete_work 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+0x34/0x90 kernel/locking/rwsem.c:54 inode_lock include/linux/fs.h:719 [inline] __generic_file_fsync+0x9e/0x190 fs/libfs.c:989 ext4_sync_file+0x8ed/0x12c0 fs/ext4/fsync.c:118 vfs_fsync_range+0x103/0x260 fs/sync.c:196 generic_write_sync include/linux/fs.h:2684 [inline] dio_complete+0x561/0x8d0 fs/direct-io.c:330 process_one_work+0x793/0x14a0 kernel/workqueue.c:2117 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251 kthread+0x30d/0x420 kernel/kthread.c:232 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404 print_req_error: I/O error, dev loop0, sector 0 UDF-fs: error (device loop5): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it UDF-fs: error (device loop5): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it UDF-fs: Scanning with blocksize 512 failed UDF-fs: warning (device loop5): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 1024 failed UDF-fs: warning (device loop5): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 2048 failed UDF-fs: warning (device loop5): udf_load_vrs: No VRS found UDF-fs: Scanning with blocksize 4096 failed 8021q: adding VLAN 0 to HW filter on device team0 bond0: Enslaving team0 as an active interface with an up link bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode syz-executor.1 (10846) used greatest stack depth: 24200 bytes left device team0 left promiscuous mode device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode UDF-fs: error (device loop5): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it bridge0: port 3(team0) entered disabled state UDF-fs: error (device loop5): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it 8021q: adding VLAN 0 to HW filter on device team0 UDF-fs: Scanning with blocksize 512 failed UDF-fs: warning (device loop5): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 1024 failed bond0: Enslaving team0 as an active interface with an up link UDF-fs: warning (device loop5): udf_load_vrs: No anchor found bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state UDF-fs: Scanning with blocksize 2048 failed bridge0: port 3(team0) entered disabled state UDF-fs: warning (device loop5): udf_load_vrs: No VRS found device team0 entered promiscuous mode UDF-fs: Scanning with blocksize 4096 failed device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode syz-executor.1 (10863) used greatest stack depth: 23936 bytes left device team0 left promiscuous mode UDF-fs: error (device loop5): udf_process_sequence: Block 99 of volume descriptor sequence is corrupted or we could not read it device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode UDF-fs: error (device loop5): udf_process_sequence: Block 1984 of volume descriptor sequence is corrupted or we could not read it bridge0: port 3(team0) entered disabled state UDF-fs: Scanning with blocksize 512 failed 8021q: adding VLAN 0 to HW filter on device team0 UDF-fs: warning (device loop5): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 1024 failed bond0: Enslaving team0 as an active interface with an up link bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state UDF-fs: warning (device loop5): udf_load_vrs: No anchor found bridge0: port 3(team0) entered disabled state UDF-fs: Scanning with blocksize 2048 failed device team0 entered promiscuous mode UDF-fs: warning (device loop5): udf_load_vrs: No VRS found device team_slave_0 entered promiscuous mode UDF-fs: Scanning with blocksize 4096 failed device team_slave_1 entered promiscuous mode device team0 left promiscuous mode device team_slave_0 left promiscuous mode device team_slave_1 left promiscuous mode bridge0: port 3(team0) entered disabled state 8021q: adding VLAN 0 to HW filter on device team0 bond0: Enslaving team0 as an active interface with an up link bond0: Releasing backup interface team0 bridge0: port 3(team0) entered blocking state bridge0: port 3(team0) entered disabled state device team0 entered promiscuous mode device team_slave_0 entered promiscuous mode device team_slave_1 entered promiscuous mode syz-executor.1 (10969) used greatest stack depth: 23872 bytes left syz-executor.3 uses obsolete (PF_INET,SOCK_PACKET) print_req_error: I/O error, dev loop6, sector 0 EXT4-fs (loop5): VFS: Can't find ext4 filesystem PF_BRIDGE: RTM_SETLINK with unknown ifindex IPv6: ADDRCONF(NETDEV_CHANGE): team0: link becomes ready A link change request failed with some changes committed already. Interface team0 may have been left with an inconsistent configuration, please check. mmap: syz-executor.4 (11327) uses deprecated remap_file_pages() syscall. See Documentation/vm/remap_file_pages.txt. EXT4-fs (loop5): VFS: Can't find ext4 filesystem EXT4-fs (loop5): VFS: Can't find ext4 filesystem PF_BRIDGE: RTM_SETLINK with unknown ifindex A link change request failed with some changes committed already. Interface team0 may have been left with an inconsistent configuration, please check. PF_BRIDGE: RTM_SETLINK with unknown ifindex PF_BRIDGE: RTM_SETLINK with unknown ifindex PF_BRIDGE: RTM_SETLINK with unknown ifindex A link change request failed with some changes committed already. Interface team0 may have been left with an inconsistent configuration, please check. IPv6: ADDRCONF(NETDEV_CHANGE): team0: link becomes ready A link change request failed with some changes committed already. Interface team0 may have been left with an inconsistent configuration, please check. unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 PF_BRIDGE: RTM_SETLINK with unknown ifindex A link change request failed with some changes committed already. Interface team0 may have been left with an inconsistent configuration, please check. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.4'.