BTRFS info (device loop2): clearing 2 ro feature flag BTRFS info (device loop2): checking UUID tree ====================================================== WARNING: possible circular locking dependency detected 4.14.307-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/10072 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/10072: #0: (&fs_info->scrub_lock){+.+.}, at: [] btrfs_scrub_dev+0x506/0xcd0 fs/btrfs/scrub.c:4217 stack backtrace: CPU: 1 PID: 10072 Comm: syz-executor.2 Not tainted 4.14.307-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/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:0x7f180708c0f9 RSP: 002b:00007f18055fe168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f18071abf80 RCX: 00007f180708c0f9 RDX: 0000000020000100 RSI: 00000000c400941b RDI: 0000000000000005 RBP: 00007f18070e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc734bf47f R14: 00007f18055fe300 R15: 0000000000022000 EXT4-fs (loop3): Ignoring removed oldalloc option EXT4-fs (loop3): mounted filesystem without journal. Opts: noload,stripe=0x0000000000000002,grpquota,oldalloc,,errors=continue EXT4-fs (loop3): Ignoring removed oldalloc option EXT4-fs (loop3): mounted filesystem without journal. Opts: noload,stripe=0x0000000000000002,grpquota,oldalloc,,errors=continue BTRFS info (device loop5): force clearing of disk cache BTRFS info (device loop5): disabling free space tree BTRFS info (device loop5): has skinny extents BTRFS info (device loop5): clearing free space tree BTRFS info (device loop5): clearing 1 ro feature flag BTRFS info (device loop5): clearing 2 ro feature flag BTRFS info (device loop5): checking UUID tree BTRFS info (device loop5): force clearing of disk cache BTRFS info (device loop5): disabling free space tree BTRFS info (device loop5): has skinny extents BTRFS info (device loop5): clearing free space tree BTRFS info (device loop5): clearing 1 ro feature flag BTRFS info (device loop5): clearing 2 ro feature flag BTRFS info (device loop5): checking UUID tree BTRFS info (device loop5): force clearing of disk cache BTRFS info (device loop5): disabling free space tree BTRFS info (device loop5): has skinny extents hfs: unable to open extent tree hfs: can't find a HFS filesystem on dev loop1 hfs: unable to open extent tree hfs: can't find a HFS filesystem on dev loop1 BTRFS info (device loop5): clearing free space tree BTRFS info (device loop5): clearing 1 ro feature flag BTRFS info (device loop5): clearing 2 ro feature flag BTRFS info (device loop5): checking UUID tree hfs: unable to open extent tree hfs: can't find a HFS filesystem on dev loop1 raw_sendmsg: syz-executor.5 forgot to set AF_INET. Fix it! hfs: unable to open extent tree hfs: can't find a HFS filesystem on dev loop1 print_req_error: I/O error, dev loop1, sector 0 Buffer I/O error on dev loop1, logical block 0, async page read print_req_error: I/O error, dev loop1, sector 1 Buffer I/O error on dev loop1, logical block 1, async page read print_req_error: I/O error, dev loop1, sector 4 Buffer I/O error on dev loop1, logical block 4, async page read print_req_error: I/O error, dev loop1, sector 5 Buffer I/O error on dev loop1, logical block 5, async page read print_req_error: I/O error, dev loop1, sector 6 Buffer I/O error on dev loop1, logical block 6, async page read print_req_error: I/O error, dev loop1, sector 7 Buffer I/O error on dev loop1, logical block 7, async page read overlayfs: failed to resolve './file0': -2 UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) netlink: 52 bytes leftover after parsing attributes in process `syz-executor.0'. nbd: socks must be embedded in a SOCK_ITEM attr netlink: 52 bytes leftover after parsing attributes in process `syz-executor.0'. nbd: socks must be embedded in a SOCK_ITEM attr netlink: 52 bytes leftover after parsing attributes in process `syz-executor.1'. UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) nbd: socks must be embedded in a SOCK_ITEM attr netlink: 52 bytes leftover after parsing attributes in process `syz-executor.1'. UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) nbd: socks must be embedded in a SOCK_ITEM attr UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) F2FS-fs (loop3): Found nat_bits in checkpoint F2FS-fs (loop3): Mounted with checkpoint version = 48b305e5 audit: type=1804 audit(1677728189.967:3): pid=10750 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.3" name="/root/syzkaller-testdir2102323549/syzkaller.B1CjZg/42/file0/bus" dev="loop3" ino=10 res=1 audit: type=1804 audit(1677728189.967:4): pid=10750 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.3" name="/root/syzkaller-testdir2102323549/syzkaller.B1CjZg/42/file0/bus" dev="loop3" ino=10 res=1 attempt to access beyond end of device loop3: rw=2049, want=40432, limit=40427 UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) audit: type=1804 audit(1677728190.597:5): pid=10822 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir418540752/syzkaller.AWv244/49/bus" dev="sda1" ino=14041 res=1 audit: type=1804 audit(1677728190.597:6): pid=10822 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.0" name="/root/syzkaller-testdir418540752/syzkaller.AWv244/49/bus" dev="sda1" ino=14041 res=1 Zero length message leads to an empty skb F2FS-fs (loop3): Found nat_bits in checkpoint 9pnet_virtio: no channels available for device 127.0.0.1 9pnet_virtio: no channels available for device 127.0.0.1 F2FS-fs (loop3): Mounted with checkpoint version = 48b305e5