From: Keith Busch <kbusch@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: syzbot <syzbot+f4353e96f7004ae5a09e@syzkaller.appspotmail.com>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Christoph Hellwig <hch@lst.de>
Subject: Re: [syzbot] [block?] BUG: corrupted list in blk_mq_request_bypass_insert
Date: Mon, 31 Aug 2026 08:58:57 -0600 [thread overview]
Message-ID: <apWWsVUm5ri7b4oR@kbusch-mbp> (raw)
In-Reply-To: <2cf45e85-176a-4209-86ad-8f389a9a4282@acm.org>
On Sat, Aug 29, 2026 at 05:16:00PM -0700, Bart Van Assche wrote:
> On 8/28/26 10:31 PM, syzbot wrote:
> > kernel BUG at lib/list_debug.c:34!
> > Call trace:
> > __list_add_valid_or_report+0x144/0x148 lib/list_debug.c:32 (P)
> > __list_add_valid include/linux/list.h:96 [inline]
> > __list_add include/linux/list.h:158 [inline]
> > list_add_tail include/linux/list.h:191 [inline]
> > blk_mq_request_bypass_insert+0x130/0x1cc block/blk-mq.c:2551
> > blk_mq_requeue_work+0x3a4/0x52c block/blk-mq.c:1560
> > process_one_work kernel/workqueue.c:3322 [inline]
> > process_scheduled_works+0x788/0x10b8 kernel/workqueue.c:3405
> > worker_thread+0x798/0xbd0 kernel/workqueue.c:3486
> > kthread+0x304/0x3d4 kernel/kthread.c:436
> > ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:838
>
> If my AI assistant got it right the root cause of this issue is as
> follows (I haven't tried to verify this):
> * Concurrent calls of nvme_reset_work() and blk_mq_requeue_work().
> * nvme_decide_disposition() does not check NVME_REQ_CANCELLED for
> non-multipath requests and returns RETRY instead of COMPLETE.
We want to be able to retry eligible commands that were caught in the
crossfire of a controller reset.
next prev parent reply other threads:[~2026-08-31 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 5:31 [syzbot] [block?] BUG: corrupted list in blk_mq_request_bypass_insert syzbot
2026-08-30 0:16 ` Bart Van Assche
2026-08-31 14:58 ` Keith Busch [this message]
2026-08-31 20:55 ` Bart Van Assche
2026-09-01 14:49 ` Keith Busch
2026-09-15 1:33 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=apWWsVUm5ri7b4oR@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+f4353e96f7004ae5a09e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.