BTRFS info (device loop1): enabling ssd optimizations
BTRFS info (device loop1): using spread ssd allocation scheme
BTRFS info (device loop1): using free space tree
BTRFS info (device loop1): has skinny extents
======================================================
WARNING: possible circular locking dependency detected
4.14.307-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.1/9729 is trying to acquire lock:
("%s-%s""btrfs", name){+.+.}, at: [<ffffffff8135cb4b>] flush_workqueue+0xcb/0x1310 kernel/workqueue.c:2622
but task is already holding lock:
(&fs_info->scrub_lock){+.+.}, at: [<ffffffff82b1bdb6>] 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.1/9729:
#0: (&fs_info->scrub_lock){+.+.}, at: [<ffffffff82b1bdb6>] btrfs_scrub_dev+0x506/0xcd0 fs/btrfs/scrub.c:4217
stack backtrace:
CPU: 1 PID: 9729 Comm: syz-executor.1 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:0x7fc4fb0c30f9
RSP: 002b:00007fc4f9635168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fc4fb1e2f80 RCX: 00007fc4fb0c30f9
RDX: 0000000020000100 RSI: 00000000c400941b RDI: 0000000000000004
RBP: 00007fc4fb11eae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc367429cf R14: 00007fc4f9635300 R15: 0000000000022000
EXT4-fs (loop5): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop5): Unsupported blocksize for fs encryption
EXT4-fs (loop0): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop0): Unsupported blocksize for fs encryption
serio: Serial port pts1
serio: Serial port pts0
EXT4-fs (loop0): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop5): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop0): Unsupported blocksize for fs encryption
EXT4-fs (loop5): Unsupported blocksize for fs encryption
serio: Serial port pts0
serio: Serial port pts1
EXT4-fs (loop0): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop0): Unsupported blocksize for fs encryption
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
kvm [9876]: vcpu0, guest rIP: 0x3445 Hyper-V unhandled rdmsr: 0x40000006
libceph: connect [d::]:6789 error -101
kvm [9876]: vcpu0, guest rIP: 0x3545 Hyper-V unhandled rdmsr: 0x4000007a
libceph: mon0 [d::]:6789 connect error
kvm [9876]: vcpu0, guest rIP: 0xf45 Hyper-V unhandled rdmsr: 0x40000017
kvm [9890]: vcpu0, guest rIP: 0x3445 Hyper-V unhandled rdmsr: 0x40000006
kvm [9905]: vcpu0, guest rIP: 0x3445 Hyper-V unhandled rdmsr: 0x40000006
kvm [9876]: vcpu0, guest rIP: 0x3045 Hyper-V unhandled rdmsr: 0x4000002e
serio: Serial port pts0
kvm [9876]: vcpu0, guest rIP: 0x3045 Hyper-V unhandled rdmsr: 0x40000019
======================================================
WARNING: the mand mount option is being deprecated and
will be removed in v5.15!
======================================================
kvm [9876]: vcpu0, guest rIP: 0x3045 Hyper-V unhandled rdmsr: 0x4000005b
kvm [9890]: vcpu0, guest rIP: 0x3645 Hyper-V unhandled rdmsr: 0x4000000d
kvm [9876]: vcpu0, guest rIP: 0x3045 Hyper-V unhandled rdmsr: 0x40000019
unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1
FAT-fs (loop3): mounting with "discard" option, but the device does not support discard
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
EXT4-fs (loop2): warning: checktime reached, running e2fsck is recommended
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
EXT4-fs (loop2): warning: checktime reached, running e2fsck is recommended
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
EXT4-fs (loop2): warning: checktime reached, running e2fsck is recommended
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
ceph: No mds server is up or the cluster is laggy
EXT4-fs (loop2): warning: checktime reached, running e2fsck is recommended
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
ceph: No mds server is up or the cluster is laggy
audit: type=1804 audit(1677723364.282:2): pid=10212 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir888396198/syzkaller.z2SfKH/15/file0/bus" dev="loop5" ino=5 res=1
attempt to access beyond end of device
loop5: rw=2049, want=2052, limit=2048
audit: type=1804 audit(1677723364.352:3): pid=10212 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir888396198/syzkaller.z2SfKH/15/file0/bus" dev="loop5" ino=5 res=1
attempt to access beyond end of device
loop5: rw=1, want=2064, limit=2048
audit: type=1804 audit(1677723364.602:4): pid=10239 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir888396198/syzkaller.z2SfKH/16/file0/bus" dev="loop5" ino=6 res=1
audit: type=1804 audit(1677723364.672:5): pid=10247 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.3" name="/root/syzkaller-testdir1198698057/syzkaller.ytA9WJ/18/file0/bus" dev="loop3" ino=7 res=1
audit: type=1804 audit(1677723364.682:6): pid=10249 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir260452611/syzkaller.LvPg7f/24/file0/bus" dev="loop0" ino=8 res=1
attempt to access beyond end of device
audit: type=1804 audit(1677723364.702:7): pid=10263 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir888396198/syzkaller.z2SfKH/16/file0/bus" dev="loop5" ino=6 res=1
loop0: rw=1, want=2064, limit=2048
attempt to access beyond end of device
loop3: rw=1, want=2064, limit=2048
audit: type=1804 audit(1677723364.752:8): pid=10271 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir260452611/syzkaller.LvPg7f/24/file0/bus" dev="loop0" ino=8 res=1
audit: type=1804 audit(1677723364.772:9): pid=10270 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.3" name="/root/syzkaller-testdir1198698057/syzkaller.ytA9WJ/18/file0/bus" dev="loop3" ino=7 res=1
audit: type=1804 audit(1677723365.122:10): pid=10254 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir3253078609/syzkaller.yxHTFn/22/file0/bus" dev="loop1" ino=9 res=1
audit: type=1804 audit(1677723365.202:11): pid=10283 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir3253078609/syzkaller.yxHTFn/22/file0/bus" dev="loop1" ino=9 res=1
attempt to access beyond end of device
attempt to access beyond end of device
loop5: rw=1, want=2064, limit=2048
loop1: rw=1, want=2064, limit=2048
attempt to access beyond end of device
loop5: rw=2049, want=2052, limit=2048
attempt to access beyond end of device
loop3: rw=2049, want=2052, limit=2048