From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, nilay@linux.ibm.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv2 2/3] nvme-multipath: rescan siblings on last path removal
Date: Fri, 27 Feb 2026 14:54:11 +0100 [thread overview]
Message-ID: <20260227135411.GB20751@lst.de> (raw)
In-Reply-To: <20260226183216.2098584-3-kbusch@meta.com>
On Thu, Feb 26, 2026 at 10:32:15AM -0800, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> When a controller's scan removes the last path to a multipath namespace
> head, sibling controllers in the same subsystem may need to rescan. A
> concurrent scan on another controller could have encountered the stale
> head with mismatched identifiers (e.g. from a recycled NSID) and failed
> to set up the namespace. Without notification, the sibling won't retry
> until the next AEN or explicit rescan.
>
> After a scan that performed last-path removals, notify all controllers
> in the subsystem to rescan by requeueing their scan work. This ensures
> that recycled NSIDs are promptly discovered by sibling controllers.
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-02-27 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 18:32 [PATCHv2 0/3] nvme: multi-path scan races fixes Keith Busch
2026-02-26 18:32 ` [PATCHv2 1/3] nvme-multipath: fix leak on try_module_get failure Keith Busch
2026-02-26 18:32 ` [PATCHv2 2/3] nvme-multipath: rescan siblings on last path removal Keith Busch
2026-02-27 6:59 ` Nilay Shroff
2026-02-27 15:34 ` Keith Busch
2026-02-27 15:57 ` Nilay Shroff
2026-02-27 13:54 ` Christoph Hellwig [this message]
2026-02-26 18:32 ` [PATCHv2 3/3] nvme: fix unmatched id's under delayed path deletion Keith Busch
2026-02-27 5:55 ` Nilay Shroff
2026-02-27 13:54 ` Christoph Hellwig
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=20260227135411.GB20751@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.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