FAT-fs (loop5): Unrecognized mount option "./bus" or missing value ====================================================== WARNING: possible circular locking dependency detected 4.14.277-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/10038 is trying to acquire lock: ("dio/%s"sb->s_id){+.+.}, at: [] flush_workqueue+0xcb/0x1310 kernel/workqueue.c:2622 but task is already holding lock: (&sb->s_type->i_mutex_key#10){+.+.}, at: [] inode_trylock include/linux/fs.h:739 [inline] (&sb->s_type->i_mutex_key#10){+.+.}, at: [] ext4_file_write_iter+0x1cc/0xd20 fs/ext4/file.c:236 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&sb->s_type->i_mutex_key#10){+.+.}: 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 -> #1 ((&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 -> #0 ("dio/%s"sb->s_id){+.+.}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 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 other info that might help us debug this: Chain exists of: "dio/%s"sb->s_id --> (&dio->complete_work) --> &sb->s_type->i_mutex_key#10 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#10); lock((&dio->complete_work)); lock(&sb->s_type->i_mutex_key#10); lock("dio/%s"sb->s_id); *** DEADLOCK *** 2 locks held by syz-executor.5/10038: #0: (sb_writers#3){.+.+}, at: [] file_start_write include/linux/fs.h:2714 [inline] #0: (sb_writers#3){.+.+}, at: [] aio_write+0x408/0x560 fs/aio.c:1552 #1: (&sb->s_type->i_mutex_key#10){+.+.}, at: [] inode_trylock include/linux/fs.h:739 [inline] #1: (&sb->s_type->i_mutex_key#10){+.+.}, at: [] ext4_file_write_iter+0x1cc/0xd20 fs/ext4/file.c:236 stack backtrace: CPU: 1 PID: 10038 Comm: syz-executor.5 Not tainted 4.14.277-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 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 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 RIP: 0033:0x7fed59dbb0e9 RSP: 002b:00007fed5870f168 EFLAGS: 00000246 ORIG_RAX: 00000000000000d1 RAX: ffffffffffffffda RBX: 00007fed59ece030 RCX: 00007fed59dbb0e9 RDX: 0000000020000540 RSI: 0000000000001801 RDI: 00007fed59ea9000 RBP: 00007fed59e1508d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffebed57d9f R14: 00007fed5870f300 R15: 0000000000022000 syz-executor.2 (10080) used greatest stack depth: 24248 bytes left L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found encrypted_key: key user:syz not found gfs2: not a GFS2 filesystem kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns encrypted_key: key user:syz not found ADFS-fs: unrecognised mount option "nfs_export=off" or missing value kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns gfs2: not a GFS2 filesystem ADFS-fs: unrecognised mount option "nfs_export=off" or missing value gfs2: not a GFS2 filesystem kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns gfs2: not a GFS2 filesystem ADFS-fs: unrecognised mount option "nfs_export=off" or missing value ADFS-fs: unrecognised mount option "nfs_export=off" or missing value gfs2: not a GFS2 filesystem kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns ADFS-fs: unrecognised mount option "nfs_export=off" or missing value gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns ADFS-fs: unrecognised mount option "nfs_export=off" or missing value gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem ADFS-fs: unrecognised mount option "nfs_export=off" or missing value gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns ADFS-fs: unrecognised mount option "nfs_export=off" or missing value gfs2: not a GFS2 filesystem ADFS-fs: unrecognised mount option "nfs_export=off" or missing value ADFS-fs: unrecognised mount option "nfs_export=off" or missing value ADFS-fs: unrecognised mount option "nfs_export=off" or missing value gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns gfs2: not a GFS2 filesystem ADFS-fs: unrecognised mount option "nfs_export=off" or missing value ADFS-fs: unrecognised mount option "nfs_export=off" or missing value ADFS-fs: unrecognised mount option "nfs_export=off" or missing value gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem gfs2: not a GFS2 filesystem ADFS-fs: unrecognised mount option "nfs_export=off" or missing value ADFS-fs: unrecognised mount option "nfs_export=off" or missing value ADFS-fs: unrecognised mount option "nfs_export=off" or missing value netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. BTRFS: device fsid f90cac8b-044b-4fa8-8bee-4b8d3da88dc2 devid 1 transid 7 /dev/loop5 netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'. BTRFS info (device loop5): disabling disk space caching BTRFS info (device loop5): force zlib compression BTRFS info (device loop5): turning on flush-on-commit BTRFS info (device loop5): has skinny extents netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'. BTRFS info (device loop5): disabling disk space caching BTRFS info (device loop5): force zlib compression BTRFS info (device loop5): turning on flush-on-commit BTRFS info (device loop5): has skinny extents BTRFS info (device loop5): disabling disk space caching BTRFS info (device loop5): force zlib compression BTRFS info (device loop5): turning on flush-on-commit BTRFS info (device loop5): has skinny extents