====================================================== WARNING: possible circular locking dependency detected 4.14.305-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/9767 is trying to acquire lock: ("%s-%s""btrfs", name){+.+.}, at: [] flush_workqueue+0xcb/0x1310 kernel/workqueue.c:2622 but task is already holding lock: (&fs_info->scrub_lock){+.+.}, at: [] btrfs_scrub_dev+0x506/0xcd0 fs/btrfs/scrub.c:4217 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&fs_info->scrub_lock){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 btrfs_scrub_dev+0x1f3/0xcd0 fs/btrfs/scrub.c:4150 btrfs_ioctl_scrub fs/btrfs/ioctl.c:4451 [inline] btrfs_ioctl+0xba8/0x5b20 fs/btrfs/ioctl.c:5681 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 -> #2 (&fs_devs->device_list_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 __reada_start_machine fs/btrfs/reada.c:765 [inline] reada_start_machine_worker+0x1d2/0xa90 fs/btrfs/reada.c:746 normal_work_helper+0x304/0x1330 fs/btrfs/async-thread.c:376 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:406 -> #1 ((&work->normal_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:406 -> #0 ("%s-%s""btrfs", name){+.+.}: 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 __btrfs_destroy_workqueue fs/btrfs/async-thread.c:436 [inline] btrfs_destroy_workqueue+0xf8/0x630 fs/btrfs/async-thread.c:447 scrub_workers_put+0x90/0x1a0 fs/btrfs/scrub.c:4075 btrfs_scrub_dev+0x536/0xcd0 fs/btrfs/scrub.c:4219 btrfs_ioctl_scrub fs/btrfs/ioctl.c:4451 [inline] btrfs_ioctl+0xba8/0x5b20 fs/btrfs/ioctl.c:5681 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 other info that might help us debug this: Chain exists of: "%s-%s""btrfs", name --> &fs_devs->device_list_mutex --> &fs_info->scrub_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&fs_info->scrub_lock); lock(&fs_devs->device_list_mutex); lock(&fs_info->scrub_lock); lock("%s-%s""btrfs", name); *** DEADLOCK *** 1 lock held by syz-executor.2/9767: #0: (&fs_info->scrub_lock){+.+.}, at: [] btrfs_scrub_dev+0x506/0xcd0 fs/btrfs/scrub.c:4217 stack backtrace: CPU: 1 PID: 9767 Comm: syz-executor.2 Not tainted 4.14.305-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023 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 __btrfs_destroy_workqueue fs/btrfs/async-thread.c:436 [inline] btrfs_destroy_workqueue+0xf8/0x630 fs/btrfs/async-thread.c:447 scrub_workers_put+0x90/0x1a0 fs/btrfs/scrub.c:4075 btrfs_scrub_dev+0x536/0xcd0 fs/btrfs/scrub.c:4219 btrfs_ioctl_scrub fs/btrfs/ioctl.c:4451 [inline] btrfs_ioctl+0xba8/0x5b20 fs/btrfs/ioctl.c:5681 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 RIP: 0033:0x7fefad03e0f9 RSP: 002b:00007fefab5b0168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fefad15df80 RCX: 00007fefad03e0f9 RDX: 0000000020000100 RSI: 00000000c400941b RDI: 0000000000000004 RBP: 00007fefad099ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff98bfff3f R14: 00007fefab5b0300 R15: 0000000000022000 BTRFS info (device loop2): enabling inode map caching BTRFS info (device loop2): trying to use backup root at mount time BTRFS info (device loop2): use zlib compression BTRFS info (device loop2): enabling ssd optimizations BTRFS info (device loop2): using spread ssd allocation scheme BTRFS info (device loop2): using free space tree BTRFS info (device loop2): has skinny extents BTRFS info (device loop2): enabling inode map caching BTRFS info (device loop2): trying to use backup root at mount time BTRFS info (device loop2): use zlib compression BTRFS info (device loop2): enabling ssd optimizations BTRFS info (device loop2): using spread ssd allocation scheme BTRFS info (device loop2): using free space tree BTRFS info (device loop2): has skinny extents EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs error (device loop3): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop3): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 266 with error 28 EXT4-fs (loop3): This should not happen!! Data will be lost EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop3): Total free blocks count 0 EXT4-fs (loop3): Free/Dirty block details EXT4-fs (loop3): free_blocks=2415919104 EXT4-fs (loop3): dirty_blocks=272 EXT4-fs (loop3): Block reservation details EXT4-fs (loop3): i_reserved_data_blocks=17 EXT4-fs error (device loop1): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop1): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 164 with error 28 EXT4-fs (loop1): This should not happen!! Data will be lost EXT4-fs (loop1): Total free blocks count 0 EXT4-fs (loop1): Free/Dirty block details EXT4-fs (loop1): free_blocks=2415919104 EXT4-fs (loop1): dirty_blocks=176 BTRFS info (device loop5): enabling inode map caching EXT4-fs (loop1): Block reservation details BTRFS info (device loop5): trying to use backup root at mount time EXT4-fs (loop1): i_reserved_data_blocks=11 BTRFS info (device loop5): use zlib compression BTRFS info (device loop5): enabling ssd optimizations BTRFS info (device loop5): using spread ssd allocation scheme BTRFS info (device loop5): using free space tree BTRFS info (device loop5): has skinny extents EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs error (device loop3): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop3): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 480 with error 28 EXT4-fs (loop3): This should not happen!! Data will be lost EXT4-fs (loop3): Total free blocks count 0 EXT4-fs (loop3): Free/Dirty block details EXT4-fs (loop3): free_blocks=2415919104 EXT4-fs (loop3): dirty_blocks=496 EXT4-fs (loop3): Block reservation details EXT4-fs (loop3): i_reserved_data_blocks=31 process 'syz-executor.4' launched './file0' with NULL argv: empty string added EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs error (device loop1): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop1): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 278 with error 28 BTRFS info (device loop5): enabling inode map caching EXT4-fs error (device loop3): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters BTRFS info (device loop5): trying to use backup root at mount time EXT4-fs (loop1): This should not happen!! Data will be lost BTRFS info (device loop5): use zlib compression EXT4-fs (loop1): Total free blocks count 0 EXT4-fs (loop3): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 178 with error 28 BTRFS info (device loop5): enabling ssd optimizations EXT4-fs (loop1): Free/Dirty block details EXT4-fs (loop1): free_blocks=2415919104 EXT4-fs (loop3): This should not happen!! Data will be lost BTRFS info (device loop5): using spread ssd allocation scheme EXT4-fs (loop3): Total free blocks count 0 EXT4-fs (loop1): dirty_blocks=288 EXT4-fs (loop1): Block reservation details EXT4-fs (loop3): Free/Dirty block details BTRFS info (device loop5): using free space tree EXT4-fs (loop3): free_blocks=2415919104 EXT4-fs (loop1): i_reserved_data_blocks=18 EXT4-fs (loop3): dirty_blocks=192 EXT4-fs (loop3): Block reservation details EXT4-fs (loop3): i_reserved_data_blocks=12 BTRFS info (device loop5): has skinny extents EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs error (device loop3): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop3): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 192 with error 28 EXT4-fs error (device loop1): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop3): This should not happen!! Data will be lost EXT4-fs (loop3): Total free blocks count 0 EXT4-fs (loop3): Free/Dirty block details EXT4-fs (loop1): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 290 with error 28 EXT4-fs (loop3): free_blocks=2415919104 EXT4-fs (loop3): dirty_blocks=208 Zero length message leads to an empty skb EXT4-fs (loop3): Block reservation details EXT4-fs (loop1): This should not happen!! Data will be lost EXT4-fs (loop3): i_reserved_data_blocks=13 EXT4-fs (loop1): Total free blocks count 0 EXT4-fs (loop1): Free/Dirty block details EXT4-fs (loop1): free_blocks=2415919104 EXT4-fs (loop1): dirty_blocks=304 EXT4-fs (loop1): Block reservation details EXT4-fs (loop1): i_reserved_data_blocks=19 UDF-fs: warning (device loop1): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 512 failed UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'.