From: "Maurizio Lombardi" <mlombard@arkamax.eu>
To: "Keith Busch" <kbusch@kernel.org>,
"Maurizio Lombardi" <mlombard@arkamax.eu>
Cc: "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 17:25:57 +0200 [thread overview]
Message-ID: <DLF57C50HQ3U.2IK671IPAW179@arkamax.eu> (raw)
In-Reply-To: <aqgQvIG17WgKKoFs@kbusch-mbp>
On Mon Sep 14, 2026 at 5:20 PM CEST, Keith Busch wrote:
> On Mon, Sep 14, 2026 at 12:16:53PM +0200, Maurizio Lombardi wrote:
>> Maybe moving the controller to CONNECTING state before exposing it to
>> sysfs will prevent the warning:
>
> I think all the transports set CONNECTING after adding the controller,
> so this would have to be duplicated for all of them, right? But why do
> we allow going from NEW to RESETTING? I don't think any of the
> transports do that anymore, so we can remove that transition instead.
Yeah, this is indeed what I was preparing to submit.
The diff I sent earlier today was just a bad idea.
Maurizio
prev parent reply other threads:[~2026-09-14 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 15:16 [syzbot] [nvme?] WARNING in nvme_loop_reset_ctrl_work syzbot
2026-09-13 15:34 ` syzbot
2026-09-14 9:21 ` Maurizio Lombardi
2026-09-14 10:16 ` Maurizio Lombardi
2026-09-14 15:20 ` Keith Busch
2026-09-14 15:25 ` Maurizio Lombardi [this message]
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=DLF57C50HQ3U.2IK671IPAW179@arkamax.eu \
--to=mlombard@arkamax.eu \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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 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.