EXT4-fs (loop2): Unrecognized mount option "@F?iow2"O+ " or missing value ====================================================== WARNING: possible circular locking dependency detected 4.14.256-syzkaller #0 Not tainted ------------------------------------------------------ kworker/1:1/23 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:3724 [inline] ext4_direct_IO+0x888/0x1b80 fs/ext4/inode.c:3865 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:1778 [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:2682 [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:1/23: #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: 23 Comm: kworker/1:1 Not tainted 4.14.256-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 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:2682 [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 EXT4-fs error (device loop5): ext4_fill_super:4371: inode #2: comm syz-executor.5: iget: root inode unallocated EXT4-fs (loop5): get root inode failed EXT4-fs (loop5): mount failed EXT4-fs error (device loop5): ext4_fill_super:4371: inode #2: comm syz-executor.5: iget: root inode unallocated EXT4-fs (loop5): get root inode failed EXT4-fs (loop5): mount failed overlayfs: missing 'lowerdir' EXT4-fs (loop0): unsupported inode size: 0 EXT4-fs (loop0): blocksize: 4096 EXT4-fs (loop0): unsupported inode size: 0 EXT4-fs (loop0): blocksize: 4096 9pnet: Insufficient options for proto=fd ip6_tables: ip6tables: counters copy to user failed while replacing table 9pnet: Insufficient options for proto=fd EXT4-fs (loop3): VFS: Can't find ext4 filesystem VPS: Can't find an adfs filesystem on dev loop5. EXT4-fs (loop3): VFS: Can't find ext4 filesystem jfs: Unrecognized mount option "18446744073709551615H'*Poꡈ^MZNS[d{unj:PiJ*>Hc" or missing value jfs: Unrecognized mount option "18446744073709551615H'*Poꡈ^MZNS[d{unj:PiJ*>Hc" or missing value ip6_tables: ip6tables: counters copy to user failed while replacing table audit: type=1804 audit(1638782386.023:15): pid=12099 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir357515169/syzkaller.LMVNFy/56/file1/bus" dev="loop0" ino=9 res=1 audit: type=1804 audit(1638782386.123:16): pid=12099 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir357515169/syzkaller.LMVNFy/56/file1/bus" dev="loop0" ino=9 res=1 nla_parse: 8 callbacks suppressed netlink: 176 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 176 bytes leftover after parsing attributes in process `syz-executor.0'. XFS (loop4): Invalid superblock magic number XFS (loop4): Invalid superblock magic number FAT-fs (loop0): Unrecognized mount option "" or missing value capability: warning: `syz-executor.5' uses 32-bit capabilities (legacy support in use) ISO 9660 Extensions: Microsoft Joliet Level 0 isofs_fill_super: get root inode failed FAT-fs (loop4): Unrecognized mount option "nnonumtail=1" or missing value ISO 9660 Extensions: Microsoft Joliet Level 0 isofs_fill_super: get root inode failed FAT-fs (loop0): Unrecognized mount option "" or missing value FAT-fs (loop5): Directory bread(block 5) failed FAT-fs (loop5): Directory bread(block 6) failed FAT-fs (loop5): Directory bread(block 7) failed FAT-fs (loop5): Directory bread(block 8) failed EXT4-fs (loop4): Unrecognized mount option "journaL" or missing value EXT4-fs (loop4): Unrecognized mount option "journaL" or missing value print_req_error: I/O error, dev loop4, sector 0 Buffer I/O error on dev loop4, logical block 0, async page read syz-executor.3 (12418): drop_caches: 2 print_req_error: I/O error, dev loop1, sector 0 8021q: adding VLAN 0 to HW filter on device batadv1 team0: Port device batadv1 added 8021q: adding VLAN 0 to HW filter on device batadv2 team0: Port device batadv2 added BTRFS info (device loop5): disk space caching is enabled BTRFS info (device loop5): has skinny extents BTRFS info (device loop5): disk space caching is enabled BTRFS info (device loop5): has skinny extents BTRFS info (device loop5): disk space caching is enabled EXT4-fs (loop4): can't mount with commit=1, fs mounted w/o journal BTRFS info (device loop5): has skinny extents NFQUEUE: number of total queues is 0 NFQUEUE: number of total queues is 0 EXT4-fs (loop4): can't mount with commit=1, fs mounted w/o journal IPv6: ADDRCONF(NETDEV_CHANGE): tunl0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): gre0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): gretap0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): erspan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): ip_vti0: link becomes ready ip6_vti0: Invalid MTU 207 requested, hw min 1280 device lo entered promiscuous mode Y4`Ҙ: renamed from lo new mount options do not match the existing superblock, will be ignored new mount options do not match the existing superblock, will be ignored ip6_tables: ip6tables: counters copy to user failed while replacing table BTRFS info (device loop5): disk space caching is enabled BTRFS info (device loop5): has skinny extents ip6_tables: ip6tables: counters copy to user failed while replacing table IPv6: NLM_F_CREATE should be specified when creating new route 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 BTRFS info (device loop5): disk space caching is enabled BTRFS info (device loop5): has skinny extents BTRFS info (device loop4): disk space caching is enabled BTRFS info (device loop4): has skinny extents BTRFS info (device loop4): disk space caching is enabled ISO 9660 Extensions: Microsoft Joliet Level 0 BTRFS info (device loop4): has skinny extents block nbd3: Receive control failed (result -107) block nbd3: shutting down sockets VFS: Can't find a Minix filesystem V1 | V2 | V3 on device loop0. BTRFS info (device loop5): disk space caching is enabled BTRFS info (device loop5): has skinny extents VFS: Can't find a Minix filesystem V1 | V2 | V3 on device loop0. isofs_fill_super: bread failed, dev=loop0, iso_blknum=34, block=68 BTRFS info (device loop5): disk space caching is enabled BTRFS info (device loop5): has skinny extents BTRFS info (device loop5): disk space caching is enabled BTRFS info (device loop5): has skinny extents BTRFS info (device loop5): disk space caching is enabled BTRFS info (device loop5): has skinny extents