syzbot


possible deadlock in blk_mq_alloc_request

Status: upstream: reported syz repro on 2024/11/06 02:40
Subsystems: block
[Documentation on labels]
Reported-by: syzbot+ca7d7c797fee31d2b474@syzkaller.appspotmail.com
First crash: 146d, last: 65d
Cause bisection: introduced by (bisect log) :
commit f1be1788a32e8fa63416ad4518bbd1a85a825c9d
Author: Ming Lei <ming.lei@redhat.com>
Date: Fri Oct 25 00:37:20 2024 +0000

  block: model freeze & enter queue as lock for supporting lockdep

Crash: WARNING: bad unlock balance in blk_mq_update_tag_set_shared (log)
Repro: syz .config
  
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly usb report (Jan 2025) 0 (1) 2025/01/17 10:35
[syzbot] [block?] possible deadlock in blk_mq_alloc_request 1 (4) 2024/12/24 12:54
Last patch testing requests (9)
Created Duration User Patch Repo Result
2025/02/04 18:45 35m retest repro linux-next OK log
2025/02/04 18:45 24m retest repro linux-next OK log
2025/02/04 18:45 25m retest repro linux-next OK log
2025/02/04 18:45 3h02m retest repro linux-next OK log
2024/11/17 12:13 12m retest repro linux-next error
2024/11/17 12:13 12m retest repro linux-next error
2024/11/17 12:13 12m retest repro linux-next error
2024/11/17 12:13 10m retest repro linux-next error
2024/11/06 03:48 21m ming.lei@redhat.com https://github.com/ming1/linux.git for-next OK log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.13.0-syzkaller-00603-g3d3a9c8b89d4 #0 Not tainted
------------------------------------------------------
kworker/3:3/6009 is trying to acquire lock:
ffff8880273c00e0 (&q->q_usage_counter(queue)#51){++++}-{0:0}, at: blk_mq_alloc_request+0x59b/0x950 block/blk-mq.c:652

but task is already holding lock:
ffff8880273c06f8 (&q->limits_lock){+.+.}-{4:4}, at: queue_limits_start_update include/linux/blkdev.h:947 [inline]
ffff8880273c06f8 (&q->limits_lock){+.+.}-{4:4}, at: sd_revalidate_disk.isra.0+0x52c/0xa8d0 drivers/scsi/sd.c:3727

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #5 (&q->limits_lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:585 [inline]
       __mutex_lock+0x19b/0xa60 kernel/locking/mutex.c:735
       queue_limits_start_update include/linux/blkdev.h:947 [inline]
       __nbd_set_size+0x2c0/0x730 drivers/block/nbd.c:351
       nbd_set_size drivers/block/nbd.c:388 [inline]
       nbd_start_device+0x8fd/0xd70 drivers/block/nbd.c:1456
       nbd_start_device_ioctl drivers/block/nbd.c:1464 [inline]
       __nbd_ioctl drivers/block/nbd.c:1539 [inline]
       nbd_ioctl+0x21a/0xfd0 drivers/block/nbd.c:1579
       blkdev_ioctl+0x276/0x6d0 block/ioctl.c:693
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:906 [inline]
       __se_sys_ioctl fs/ioctl.c:892 [inline]
       __x64_sys_ioctl+0x190/0x200 fs/ioctl.c:892
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #4 (&q->q_usage_counter(io)#50){++++}-{0:0}:
       bio_queue_enter block/blk.h:75 [inline]
       blk_mq_submit_bio+0x1fb6/0x24c0 block/blk-mq.c:3090
       __submit_bio+0x384/0x540 block/blk-core.c:629
       __submit_bio_noacct_mq block/blk-core.c:710 [inline]
       submit_bio_noacct_nocheck+0x698/0xd70 block/blk-core.c:739
       submit_bio_noacct+0x93a/0x1e20 block/blk-core.c:868
       submit_bh fs/buffer.c:2819 [inline]
       block_read_full_folio+0x812/0xa50 fs/buffer.c:2446
       filemap_read_folio+0xc6/0x2a0 mm/filemap.c:2357
       filemap_update_page mm/filemap.c:2441 [inline]
       filemap_get_pages+0x155f/0x1be0 mm/filemap.c:2562
       filemap_read+0x3ca/0xd70 mm/filemap.c:2637
       blkdev_read_iter+0x187/0x480 block/fops.c:770
       new_sync_read fs/read_write.c:484 [inline]
       vfs_read+0x87f/0xbe0 fs/read_write.c:565
       ksys_read+0x12b/0x250 fs/read_write.c:708
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #3 (mapping.invalidate_lock#2){++++}-{4:4}:
       down_read+0x9a/0x330 kernel/locking/rwsem.c:1524
       filemap_invalidate_lock_shared include/linux/fs.h:886 [inline]
       filemap_fault+0x62c/0x2820 mm/filemap.c:3342
       __do_fault+0x10a/0x490 mm/memory.c:4907
       do_read_fault mm/memory.c:5322 [inline]
       do_fault mm/memory.c:5456 [inline]
       do_pte_missing+0xebd/0x3e00 mm/memory.c:3979
       handle_pte_fault mm/memory.c:5801 [inline]
       __handle_mm_fault+0x103c/0x2a40 mm/memory.c:5944
       handle_mm_fault+0x3fa/0xaa0 mm/memory.c:6112
       do_user_addr_fault+0x7a3/0x13f0 arch/x86/mm/fault.c:1389
       handle_page_fault arch/x86/mm/fault.c:1481 [inline]
       exc_page_fault+0x5c/0xc0 arch/x86/mm/fault.c:1539
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
       copy_user_generic arch/x86/include/asm/uaccess_64.h:126 [inline]
       raw_copy_from_user arch/x86/include/asm/uaccess_64.h:141 [inline]
       copy_from_user_iter lib/iov_iter.c:55 [inline]
       iterate_ubuf include/linux/iov_iter.h:30 [inline]
       iterate_and_advance2 include/linux/iov_iter.h:300 [inline]
       iterate_and_advance include/linux/iov_iter.h:328 [inline]
       __copy_from_iter lib/iov_iter.c:249 [inline]
       _copy_from_iter+0x380/0x1560 lib/iov_iter.c:260
       copy_from_iter include/linux/uio.h:219 [inline]
       copy_from_iter_full include/linux/uio.h:236 [inline]
       tipc_msg_build+0x308/0x1120 net/tipc/msg.c:408
       __tipc_sendstream+0x6fa/0x1190 net/tipc/socket.c:1615
       tipc_sendstream+0x4f/0x70 net/tipc/socket.c:1546
       sock_sendmsg_nosec net/socket.c:711 [inline]
       __sock_sendmsg net/socket.c:726 [inline]
       sock_write_iter+0x4fe/0x5b0 net/socket.c:1147
       new_sync_write fs/read_write.c:586 [inline]
       vfs_write+0x5ae/0x1150 fs/read_write.c:679
       ksys_write+0x207/0x250 fs/read_write.c:731
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&mm->mmap_lock){++++}-{4:4}:
       __might_fault mm/memory.c:6751 [inline]
       __might_fault+0x11b/0x190 mm/memory.c:6744
       _inline_copy_from_user include/linux/uaccess.h:162 [inline]
       _copy_from_user+0x29/0xd0 lib/usercopy.c:18
       copy_from_user include/linux/uaccess.h:212 [inline]
       __blk_trace_setup+0xa8/0x180 kernel/trace/blktrace.c:626
       blk_trace_setup+0x47/0x70 kernel/trace/blktrace.c:648
       sg_ioctl_common drivers/scsi/sg.c:1114 [inline]
       sg_ioctl+0x65e/0x2750 drivers/scsi/sg.c:1156
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:906 [inline]
       __se_sys_ioctl fs/ioctl.c:892 [inline]
       __x64_sys_ioctl+0x190/0x200 fs/ioctl.c:892
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&q->debugfs_mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:585 [inline]
       __mutex_lock+0x19b/0xa60 kernel/locking/mutex.c:735
       blk_mq_init_sched+0x42b/0x640 block/blk-mq-sched.c:473
       elevator_init_mq+0x2cd/0x420 block/elevator.c:610
       add_disk_fwnode+0x113/0x1300 block/genhd.c:413
       sd_probe+0xa86/0x1000 drivers/scsi/sd.c:4024
       call_driver_probe drivers/base/dd.c:579 [inline]
       really_probe+0x23e/0xa90 drivers/base/dd.c:658
       __driver_probe_device+0x1de/0x440 drivers/base/dd.c:800
       driver_probe_device+0x4c/0x1b0 drivers/base/dd.c:830
       __device_attach_driver+0x1df/0x310 drivers/base/dd.c:958
       bus_for_each_drv+0x157/0x1e0 drivers/base/bus.c:459
       __device_attach_async_helper+0x1d3/0x290 drivers/base/dd.c:987
       async_run_entry_fn+0x9c/0x530 kernel/async.c:129
       process_one_work+0x9c5/0x1ba0 kernel/workqueue.c:3236
       process_scheduled_works kernel/workqueue.c:3317 [inline]
       worker_thread+0x6c8/0xf00 kernel/workqueue.c:3398
       kthread+0x2c1/0x3a0 kernel/kthread.c:389
       ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #0 (&q->q_usage_counter(queue)#51){++++}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3161 [inline]
       check_prevs_add kernel/locking/lockdep.c:3280 [inline]
       validate_chain kernel/locking/lockdep.c:3904 [inline]
       __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226
       lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849
       blk_queue_enter+0x50f/0x640 block/blk-core.c:328
       blk_mq_alloc_request+0x59b/0x950 block/blk-mq.c:652
       scsi_alloc_request drivers/scsi/scsi_lib.c:1225 [inline]
       scsi_execute_cmd+0x1da/0xf40 drivers/scsi/scsi_lib.c:307
       read_capacity_16+0x213/0xe10 drivers/scsi/sd.c:2655
       sd_read_capacity drivers/scsi/sd.c:2824 [inline]
       sd_revalidate_disk.isra.0+0x1a06/0xa8d0 drivers/scsi/sd.c:3734
       scsi_rescan_device+0x243/0x340 drivers/scsi/scsi_scan.c:1715
       ata_scsi_dev_rescan+0x1cb/0x470 drivers/ata/libata-scsi.c:4902
       process_one_work+0x9c5/0x1ba0 kernel/workqueue.c:3236
       process_scheduled_works kernel/workqueue.c:3317 [inline]
       worker_thread+0x6c8/0xf00 kernel/workqueue.c:3398
       kthread+0x2c1/0x3a0 kernel/kthread.c:389
       ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

other info that might help us debug this:

Chain exists of:
  &q->q_usage_counter(queue)#51 --> &q->q_usage_counter(io)#50 --> &q->limits_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&q->limits_lock);
                               lock(&q->q_usage_counter(io)#50);
                               lock(&q->limits_lock);
  rlock(&q->q_usage_counter(queue)#51);

 *** DEADLOCK ***

5 locks held by kworker/3:3/6009:
 #0: ffff88801b088948 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x1293/0x1ba0 kernel/workqueue.c:3211
 #1: ffffc90003d27d80 ((work_completion)(&(&ap->scsi_rescan_task)->work)){+.+.}-{0:0}, at: process_one_work+0x921/0x1ba0 kernel/workqueue.c:3212
 #2: ffff888026ba4358 (&ap->scsi_scan_mutex){+.+.}-{4:4}, at: ata_scsi_dev_rescan+0x3e/0x470 drivers/ata/libata-scsi.c:4874
 #3: ffff888026a52378 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1014 [inline]
 #3: ffff888026a52378 (&dev->mutex){....}-{4:4}, at: scsi_rescan_device+0x27/0x340 drivers/scsi/scsi_scan.c:1691
 #4: ffff8880273c06f8 (&q->limits_lock){+.+.}-{4:4}, at: queue_limits_start_update include/linux/blkdev.h:947 [inline]
 #4: ffff8880273c06f8 (&q->limits_lock){+.+.}-{4:4}, at: sd_revalidate_disk.isra.0+0x52c/0xa8d0 drivers/scsi/sd.c:3727

stack backtrace:
CPU: 3 UID: 0 PID: 6009 Comm: kworker/3:3 Not tainted 6.13.0-syzkaller-00603-g3d3a9c8b89d4 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: events ata_scsi_dev_rescan
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_circular_bug+0x419/0x5d0 kernel/locking/lockdep.c:2074
 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2206
 check_prev_add kernel/locking/lockdep.c:3161 [inline]
 check_prevs_add kernel/locking/lockdep.c:3280 [inline]
 validate_chain kernel/locking/lockdep.c:3904 [inline]
 __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226
 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849
 blk_queue_enter+0x50f/0x640 block/blk-core.c:328
 blk_mq_alloc_request+0x59b/0x950 block/blk-mq.c:652
 scsi_alloc_request drivers/scsi/scsi_lib.c:1225 [inline]
 scsi_execute_cmd+0x1da/0xf40 drivers/scsi/scsi_lib.c:307
 read_capacity_16+0x213/0xe10 drivers/scsi/sd.c:2655
 sd_read_capacity drivers/scsi/sd.c:2824 [inline]
 sd_revalidate_disk.isra.0+0x1a06/0xa8d0 drivers/scsi/sd.c:3734
 scsi_rescan_device+0x243/0x340 drivers/scsi/scsi_scan.c:1715
 ata_scsi_dev_rescan+0x1cb/0x470 drivers/ata/libata-scsi.c:4902
 process_one_work+0x9c5/0x1ba0 kernel/workqueue.c:3236
 process_scheduled_works kernel/workqueue.c:3317 [inline]
 worker_thread+0x6c8/0xf00 kernel/workqueue.c:3398
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
SELinux: failure in sel_netif_sid_slow(), invalid network interface (16)

Crashes (827):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/01/21 10:56 upstream 3d3a9c8b89d4 6e87cfa2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/20 19:31 upstream ffd294d346d1 6e87cfa2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/20 12:50 upstream ffd294d346d1 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/20 12:33 upstream ffd294d346d1 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/19 01:02 upstream 595523945be0 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/18 19:40 upstream 595523945be0 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/18 18:20 upstream 595523945be0 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/18 10:47 upstream ad26fc09dabf f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/18 07:49 upstream ad26fc09dabf f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/18 03:54 upstream ad26fc09dabf f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/16 23:24 upstream ce69b4019001 f9e07a6e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/16 19:05 upstream ce69b4019001 f9e07a6e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/16 00:28 upstream 619f0b6fad52 968edaf4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/15 14:35 upstream 619f0b6fad52 968edaf4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/14 14:27 upstream c45323b7560e 0dce2409 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/13 22:33 upstream c45323b7560e b1f1cd88 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/13 19:47 upstream 5bc55a333a2f 249ceea9 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/13 07:20 upstream be548645527a 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/13 04:33 upstream be548645527a 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/13 03:08 upstream be548645527a 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/13 00:26 upstream be548645527a 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/12 14:08 upstream b62cef9a5c67 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blk_mq_alloc_request
2025/01/21 13:57 upstream 3d3a9c8b89d4 6e87cfa2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/21 02:52 upstream ffd294d346d1 6e87cfa2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/20 23:39 upstream ffd294d346d1 6e87cfa2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/19 14:30 upstream fda5e3f28400 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/19 11:41 upstream fda5e3f28400 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/19 07:12 upstream fda5e3f28400 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/19 04:16 upstream fda5e3f28400 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/19 03:11 upstream fda5e3f28400 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/18 23:32 upstream 595523945be0 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/18 21:49 upstream 595523945be0 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/18 13:23 upstream 595523945be0 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/17 22:13 upstream 9bffa1ad25b8 bb91bdd4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/17 21:56 upstream 9bffa1ad25b8 bb91bdd4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/17 02:17 upstream ce69b4019001 f9e07a6e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/16 08:18 upstream 619f0b6fad52 968edaf4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/16 06:00 upstream 619f0b6fad52 968edaf4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/15 13:25 upstream 619f0b6fad52 968edaf4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/15 04:14 upstream c3812b15000c 7315a7cf .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/15 01:20 upstream c3812b15000c 7315a7cf .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/14 23:57 upstream c3812b15000c 7315a7cf .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/14 08:04 upstream c45323b7560e b1f1cd88 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/14 04:51 upstream c45323b7560e b1f1cd88 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/13 11:42 upstream 5bc55a333a2f 249ceea9 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/13 08:37 upstream be548645527a 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/12 16:49 upstream b62cef9a5c67 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2025/01/12 15:13 upstream b62cef9a5c67 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blk_mq_alloc_request
2024/11/03 12:09 linux-next c88416ba074a f00eed24 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_mq_alloc_request
2024/11/02 19:16 linux-next c88416ba074a f00eed24 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_mq_alloc_request
2024/11/02 15:27 linux-next c88416ba074a f00eed24 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_mq_alloc_request
2024/11/02 14:11 linux-next c88416ba074a f00eed24 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_mq_alloc_request
2024/11/02 02:37 linux-next c88416ba074a f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blk_mq_alloc_request
* Struck through repros no longer work on HEAD.