syzbot


possible deadlock in loop_set_status

Status: upstream: reported C repro on 2024/11/23 14:42
Subsystems: block
[Documentation on labels]
Reported-by: syzbot+9b145229d11aa73e4571@syzkaller.appspotmail.com
First crash: 173d, last: now
Cause bisection: introduced by (bisect log) :
commit ffa1e7ada456087c2402b37cd6b2863ced29aff0
Author: Thomas HellstrΓΆm <thomas.hellstrom@linux.intel.com>
Date: Tue Mar 18 09:55:48 2025 +0000

  block: Make request_queue lockdep splats show up earlier

Crash: possible deadlock in loop_set_status (log)
Repro: C syz .config
  
Discussions (4)
Title Replies (including bot) Last reply
[syzbot] [block?] possible deadlock in loop_set_status 2 (6) 2025/05/02 11:51
[syzbot] Monthly block report (Apr 2025) 0 (1) 2025/04/24 13:06
[syzbot] Monthly block report (Mar 2025) 0 (1) 2025/03/24 18:56
[syzbot] Monthly block report (Jan 2025) 0 (1) 2025/01/20 13:06
Last patch testing requests (1)
Created Duration User Patch Repo Result
2025/03/01 13:48 26m hdanton@sina.com patch upstream OK log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.15.0-rc3-syzkaller-00283-gf1a3944c860b #0 Not tainted
------------------------------------------------------
syz-executor354/5827 is trying to acquire lock:
ffffffff8f657248 (uevent_sock_mutex){+.+.}-{4:4}, at: uevent_net_broadcast_untagged lib/kobject_uevent.c:317 [inline]
ffffffff8f657248 (uevent_sock_mutex){+.+.}-{4:4}, at: kobject_uevent_net_broadcast+0x27e/0x560 lib/kobject_uevent.c:410

but task is already holding lock:
ffff888143fb27a8 (&q->q_usage_counter(io)#24){++++}-{0:0}, at: blk_mq_freeze_queue include/linux/blk-mq.h:928 [inline]
ffff888143fb27a8 (&q->q_usage_counter(io)#24){++++}-{0:0}, at: loop_set_status+0x225/0xaf0 drivers/block/loop.c:1215

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&q->q_usage_counter(io)#24){++++}-{0:0}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
       blk_alloc_queue+0x538/0x620 block/blk-core.c:461
       blk_mq_alloc_queue block/blk-mq.c:4348 [inline]
       __blk_mq_alloc_disk+0x164/0x350 block/blk-mq.c:4395
       loop_add+0x41d/0xae0 drivers/block/loop.c:1990
       loop_init+0x173/0x230 drivers/block/loop.c:2225
       do_one_initcall+0x233/0x820 init/main.c:1257
       do_initcall_level+0x137/0x1f0 init/main.c:1319
       do_initcalls+0x69/0xd0 init/main.c:1335
       kernel_init_freeable+0x3d9/0x570 init/main.c:1567
       kernel_init+0x1d/0x1d0 init/main.c:1457
       ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #1 (fs_reclaim){+.+.}-{0:0}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
       __fs_reclaim_acquire mm/page_alloc.c:4064 [inline]
       fs_reclaim_acquire+0x72/0x100 mm/page_alloc.c:4078
       might_alloc include/linux/sched/mm.h:318 [inline]
       slab_pre_alloc_hook mm/slub.c:4112 [inline]
       slab_alloc_node mm/slub.c:4190 [inline]
       kmem_cache_alloc_node_noprof+0x47/0x3c0 mm/slub.c:4262
       __alloc_skb+0x112/0x2d0 net/core/skbuff.c:658
       alloc_skb include/linux/skbuff.h:1340 [inline]
       alloc_uevent_skb+0x7d/0x230 lib/kobject_uevent.c:289
       uevent_net_broadcast_untagged lib/kobject_uevent.c:326 [inline]
       kobject_uevent_net_broadcast+0x2fa/0x560 lib/kobject_uevent.c:410
       kobject_uevent_env+0x55b/0x8c0 lib/kobject_uevent.c:608
       kobject_synth_uevent+0x527/0xb00 lib/kobject_uevent.c:207
       bus_uevent_store+0x115/0x170 drivers/base/bus.c:832
       kernfs_fop_write_iter+0x375/0x4f0 fs/kernfs/file.c:334
       new_sync_write fs/read_write.c:591 [inline]
       vfs_write+0x548/0xa90 fs/read_write.c:684
       ksys_write+0x145/0x250 fs/read_write.c:736
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (uevent_sock_mutex){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3166 [inline]
       check_prevs_add kernel/locking/lockdep.c:3285 [inline]
       validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909
       __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746
       uevent_net_broadcast_untagged lib/kobject_uevent.c:317 [inline]
       kobject_uevent_net_broadcast+0x27e/0x560 lib/kobject_uevent.c:410
       kobject_uevent_env+0x55b/0x8c0 lib/kobject_uevent.c:608
       loop_set_size drivers/block/loop.c:211 [inline]
       loop_set_status+0x4d1/0xaf0 drivers/block/loop.c:1230
       lo_ioctl+0xb41/0x22e0 drivers/block/loop.c:-1
       blkdev_ioctl+0x5a5/0x6d0 block/ioctl.c:704
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:906 [inline]
       __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:892
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  uevent_sock_mutex --> fs_reclaim --> &q->q_usage_counter(io)#24

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&q->q_usage_counter(io)#24);
                               lock(fs_reclaim);
                               lock(&q->q_usage_counter(io)#24);
  lock(uevent_sock_mutex);

 *** DEADLOCK ***

3 locks held by syz-executor354/5827:
 #0: ffff888024209368 (&lo->lo_mutex){+.+.}-{4:4}, at: loop_set_status+0x2a/0xaf0 drivers/block/loop.c:1199
 #1: ffff888143fb27a8 (&q->q_usage_counter(io)#24){++++}-{0:0}, at: blk_mq_freeze_queue include/linux/blk-mq.h:928 [inline]
 #1: ffff888143fb27a8 (&q->q_usage_counter(io)#24){++++}-{0:0}, at: loop_set_status+0x225/0xaf0 drivers/block/loop.c:1215
 #2: ffff888143fb27e0 (&q->q_usage_counter(queue)#20){+.+.}-{0:0}, at: blk_mq_freeze_queue include/linux/blk-mq.h:928 [inline]
 #2: ffff888143fb27e0 (&q->q_usage_counter(queue)#20){+.+.}-{0:0}, at: loop_set_status+0x225/0xaf0 drivers/block/loop.c:1215

stack backtrace:
CPU: 0 UID: 0 PID: 5827 Comm: syz-executor354 Not tainted 6.15.0-rc3-syzkaller-00283-gf1a3944c860b #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2079
 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2211
 check_prev_add kernel/locking/lockdep.c:3166 [inline]
 check_prevs_add kernel/locking/lockdep.c:3285 [inline]
 validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909
 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
 __mutex_lock_common kernel/locking/mutex.c:601 [inline]
 __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746
 uevent_net_broadcast_untagged lib/kobject_uevent.c:317 [inline]
 kobject_uevent_net_broadcast+0x27e/0x560 lib/kobject_uevent.c:410
 kobject_uevent_env+0x55b/0x8c0 lib/kobject_uevent.c:608
 loop_set_size drivers/block/loop.c:211 [inline]
 loop_set_status+0x4d1/0xaf0 drivers/block/loop.c:1230
 lo_ioctl+0xb41/0x22e0 drivers/block/loop.c:-1
 blkdev_ioctl+0x5a5/0x6d0 block/ioctl.c:704
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:906 [inline]
 __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:892
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f90cf63a939
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe0d3db488 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f90cf63a939
RDX: 00002000000001c0 RSI: 0000000000004c02 RDI: 0000000000000003
RBP: 00007f90cf6ad5f0 R08: 0000000000000006 R09: 0000000000000006
R10: 0000000000000006 R11: 0000000000000246 R12: 0000000000000001
R13: 431bde82d7b634db R14: 0000000000000001 R15: 0000000000000001
 </TASK>

Crashes (13853):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/26 20:42 upstream f1a3944c860b c6b4fb39 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 05:48 upstream ea34704d6ad7 77908e5f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/05/10 04:49 upstream ea34704d6ad7 77908e5f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/05/01 19:46 upstream 4f79eaa2ceac 51b137cd .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/05/01 18:03 upstream 4f79eaa2ceac 51b137cd .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/04/28 02:39 upstream b4432656b36e c6b4fb39 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/04/25 20:07 upstream 02ddfb981de8 dea5c7e4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/04/25 15:47 upstream 02ddfb981de8 dea5c7e4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/03/01 10:17 upstream 276f98efb64a 67cf5345 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro #1 (corrupt fs)] [mounted in repro #2] [mounted in repro #3 (clean fs)] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/05/12 02:46 upstream cd802e7e5f1e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/12 01:43 upstream cd802e7e5f1e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in loop_set_status
2025/05/12 01:42 upstream cd802e7e5f1e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in loop_set_status
2025/05/12 00:14 upstream cd802e7e5f1e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/11 20:01 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/11 18:45 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in loop_set_status
2025/05/11 18:45 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/11 15:55 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/11 14:54 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/11 11:44 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in loop_set_status
2025/05/11 11:28 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/11 09:51 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/11 08:44 upstream 345030986df8 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in loop_set_status
2025/05/11 06:55 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in loop_set_status
2025/05/11 06:44 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/11 03:40 upstream 345030986df8 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in loop_set_status
2025/05/11 01:53 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 23:55 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 22:31 upstream bec6f00f120e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in loop_set_status
2025/05/10 20:37 upstream 0e1329d4045c 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in loop_set_status
2025/05/10 18:24 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 17:20 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 17:01 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 15:48 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 14:44 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 13:44 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 12:56 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 11:47 upstream 0e1329d4045c 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in loop_set_status
2025/05/10 10:45 upstream 0e1329d4045c 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in loop_set_status
2025/05/10 10:26 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 09:17 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in loop_set_status
2025/05/10 07:05 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 04:42 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/10 02:56 upstream 3013c33dcbd9 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in loop_set_status
2025/05/09 22:13 upstream 3013c33dcbd9 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in loop_set_status
2025/05/09 21:56 upstream 3013c33dcbd9 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in loop_set_status
2025/05/03 10:16 upstream 95d3481af6dc b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in loop_set_status
2025/05/11 21:26 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in loop_set_status
2025/05/11 17:23 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in loop_set_status
2025/05/11 16:06 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in loop_set_status
2025/05/11 13:53 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in loop_set_status
2025/05/11 12:48 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in loop_set_status
2025/05/11 05:07 upstream 345030986df8 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in loop_set_status
2025/05/11 02:27 upstream 345030986df8 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in loop_set_status
2025/05/10 08:09 upstream 0e1329d4045c 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in loop_set_status
2025/05/10 01:48 upstream ea34704d6ad7 77908e5f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/05/10 00:02 upstream ea34704d6ad7 77908e5f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in loop_set_status
2024/11/23 11:42 upstream 06afb0f36106 68da6d95 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in loop_set_status
2024/11/19 14:40 upstream 158f238aa69d 571351cb .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in loop_set_status
2025/04/17 06:58 linux-next 01c6df60d5d4 23b969b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in loop_set_status
2025/05/09 14:49 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c32f8dc5aaf9 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in loop_set_status
* Struck through repros no longer work on HEAD.