Hello, syzbot found the following issue on: HEAD commit: 43fb83c17ba2 Merge tag 'soc-arm-6.13' of git://git.kernel... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12280ec0580000 kernel config: https://syzkaller.appspot.com/x/.config?x=e796b1bf154f93a7 dashboard link: https://syzkaller.appspot.com/bug?extid=f53c29806b4b263165f3 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/cdcbc016316b/disk-43fb83c1.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/f82505daa7c2/vmlinux-43fb83c1.xz kernel image: https://storage.googleapis.com/syzbot-assets/74b0b41d70c6/bzImage-43fb83c1.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+f53c29806b4b263165f3@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ statistics for priority 0: i 8 m 0 d 8 c 0 WARNING: CPU: 0 PID: 7130 at block/mq-deadline.c:562 dd_exit_sched+0x2a8/0x3a0 block/mq-deadline.c:559 Modules linked in: CPU: 0 UID: 0 PID: 7130 Comm: kworker/u8:10 Not tainted 6.12.0-syzkaller-03657-g43fb83c17ba2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 Workqueue: nbd-del nbd_dev_remove_work RIP: 0010:dd_exit_sched+0x2a8/0x3a0 block/mq-deadline.c:559 Code: b6 44 25 00 84 c0 0f 85 dd 00 00 00 44 8b 0b 48 c7 c7 00 3a 5f 8c 8b 74 24 04 8b 54 24 08 44 89 f9 45 89 e8 e8 c9 af b2 fc 90 <0f> 0b 90 90 e9 03 ff ff ff 48 c7 c1 60 e7 1c 90 80 e1 07 80 c1 03 RSP: 0018:ffffc90004247910 EFLAGS: 00010246 RAX: 83929aab89e5bc00 RBX: ffff888024eb5c5c RCX: ffff888027a51e00 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000 RBP: 1ffff110049d6b8b R08: ffffffff8155f352 R09: fffffbfff1cfa88c R10: dffffc0000000000 R11: fffffbfff1cfa88c R12: dffffc0000000000 R13: 0000000000000008 R14: ffff888024eb5c00 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe1d01f3f98 CR3: 0000000073672000 CR4: 00000000003526f0 Call Trace: <TASK> blk_mq_exit_sched+0x2ce/0x4a0 block/blk-mq-sched.c:547 elevator_exit+0x5e/0x80 block/elevator.c:159 del_gendisk+0x7a8/0x930 block/genhd.c:735 nbd_dev_remove drivers/block/nbd.c:264 [inline] nbd_dev_remove_work+0x47/0xe0 drivers/block/nbd.c:280 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
