From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: hch@lst.de, kbusch@kernel.org, hare@suse.de, dwagner@suse.de,
sagi@grimberg.me, linux-nvme@lists.infradead.org,
a.manzanares@samsung.com, joshiiitr@gmail.com
Subject: Re: [PATCH] nvme-multipath: fix multipath path scan
Date: Wed, 16 Feb 2022 09:11:48 +0100 [thread overview]
Message-ID: <20220216081148.GA10851@lst.de> (raw)
In-Reply-To: <20220216061305.45360-1-joshi.k@samsung.com>
On Wed, Feb 16, 2022 at 11:43:05AM +0530, Kanchan Joshi wrote:
> commit e7d65803e2bb ("nvme-multipath: revalidate paths during rescan")
> introduced NVME_NS_READY flag. nvme_path_is_disabled() declares path/ns
> to be disabled if this flag is not found to be set.
> This causes side-effect on namespace for which block-interface is not
> fully up.
Hmm. This means for non-bdev namespaces we error out somewhere in
nvme_update_ns_info. Where do we fail here, nvme_configure_metadata?
next prev parent reply other threads:[~2022-02-16 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220216061807epcas5p1a349815c50db8f3539c30e2dd569232f@epcas5p1.samsung.com>
2022-02-16 6:13 ` [PATCH] nvme-multipath: fix multipath path scan Kanchan Joshi
2022-02-16 8:11 ` Christoph Hellwig [this message]
2022-02-16 12:48 ` Kanchan Joshi
2022-02-16 12:57 ` Daniel Wagner
2022-02-16 13:20 ` Christoph Hellwig
2022-02-16 14:03 ` Kanchan Joshi
2022-02-16 14:47 ` Adam Manzanares
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=20220216081148.GA10851@lst.de \
--to=hch@lst.de \
--cc=a.manzanares@samsung.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=joshi.k@samsung.com \
--cc=joshiiitr@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.