From: Keith Busch <kbusch@kernel.org>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: mlombard@arkamax.eu, mkhalfella@purestorage.com,
randyj@purestorage.com, hch@lst.de,
linux-nvme@lists.infradead.org, dwagner@suse.de,
emilne@redhat.com
Subject: Re: [PATCH 1/1] nvme-fc: Do not cancel requests in io target before it is initialized
Date: Wed, 10 Jun 2026 08:35:18 -0600 [thread overview]
Message-ID: <ail2JuRcg6lE007b@kbusch-mbp> (raw)
In-Reply-To: <20260528092734.258899-2-mlombard@redhat.com>
On Thu, May 28, 2026 at 11:27:34AM +0200, Maurizio Lombardi wrote:
> From: Mohamed Khalfella <mkhalfella@purestorage.com>
>
> A new nvme-fc controller in CONNECTING state sees admin request timeout
> schedules ctrl->ioerr_work to abort inflight requests. This ends up
> calling __nvme_fc_abort_outstanding_ios() which aborts requests in both
> admin and io tagsets. In case fc_ctrl->tag_set was not initialized we
> see the warning below. This is because ctrl.queue_count is initialized
> early in nvme_fc_alloc_ctrl().
Thanks, applied to nvme-7.2.
next prev parent reply other threads:[~2026-06-10 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 9:27 [PATCH 0/1] Fix a kernel panic in nvme-fc Maurizio Lombardi
2026-05-28 9:27 ` [PATCH 1/1] nvme-fc: Do not cancel requests in io target before it is initialized Maurizio Lombardi
2026-06-01 7:12 ` Christoph Hellwig
2026-06-01 9:47 ` Daniel Wagner
2026-06-01 10:28 ` Maurizio Lombardi
2026-06-01 14:16 ` Daniel Wagner
2026-06-10 11:35 ` Hannes Reinecke
2026-06-10 14:35 ` Keith Busch [this message]
2026-06-10 9:23 ` [PATCH 0/1] Fix a kernel panic in nvme-fc 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=ail2JuRcg6lE007b@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=dwagner@suse.de \
--cc=emilne@redhat.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=mkhalfella@purestorage.com \
--cc=mlombard@arkamax.eu \
--cc=mlombard@redhat.com \
--cc=randyj@purestorage.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