mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Maurizio Lombardi" <mlombard@arkamax.eu>
To: "syzbot" <syzbot+4a1d521d19d6321f5aad@syzkaller.appspotmail.com>,
	<hch@lst.de>, <kch@nvidia.com>, <linux-kernel@vger.kernel.org>,
	<linux-nvme@lists.infradead.org>, <sagi@grimberg.me>,
	<syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] [nvme?] WARNING in nvme_loop_reset_ctrl_work
Date: Mon, 14 Sep 2026 11:21:55 +0200	[thread overview]
Message-ID: <DLEXGM8VZOW9.1J9A20FEP43RM@arkamax.eu> (raw)
In-Reply-To: <6aa6c282.4c28b7d0.c1bba.000d.GAE@google.com>

On Sun Sep 13, 2026 at 5:34 PM CEST, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit:    2f0c1cf72f46 Merge tag 's390-7.3-3' of git://git.kernel.or..
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> console output: https://syzkaller.appspot.com/x/log.txt?x=159b19f9580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
> dashboard link: https://syzkaller.appspot.com/bug?extid=4a1d521d19d6321f5aad
> compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1074f615580000


It seems that a reset operation is enqueued before the controller
initialization is completed.

when the nvme_loop_reset_ctrl_work() finally runs, it will find the
controller in LIVE state, thus hitting the WARN_ON().

Maurizio

  reply	other threads:[~2026-09-14  9:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 15:16 syzbot
2026-09-13 15:34 ` syzbot
2026-09-14  9:21   ` Maurizio Lombardi [this message]
2026-09-14 10:16     ` Maurizio Lombardi
2026-09-14 15:20       ` Keith Busch
2026-09-14 15:25         ` Maurizio Lombardi

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=DLEXGM8VZOW9.1J9A20FEP43RM@arkamax.eu \
    --to=mlombard@arkamax.eu \
    --cc=hch@lst.de \
    --cc=kch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=syzbot+4a1d521d19d6321f5aad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®