From: Chao Leng <lengchao@huawei.com>
To: Daniel Wagner <dwagner@suse.de>, <linux-nvme@lists.infradead.org>
Cc: Sagi Grimberg <sagi@grimberg.me>, <linux-kernel@vger.kernel.org>,
"Jens Axboe" <axboe@fb.com>, Hannes Reinecke <hare@suse.de>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] nvme-multipath: Early exit if no path is available
Date: Thu, 28 Jan 2021 09:31:30 +0800 [thread overview]
Message-ID: <db9baae0-547c-7ff4-8b2c-0b95f14be67c@huawei.com> (raw)
In-Reply-To: <20210127103033.15318-1-dwagner@suse.de>
On 2021/1/27 18:30, Daniel Wagner wrote:
> nvme_round_robin_path() should test if the return ns pointer is
> valid. nvme_next_ns() will return a NULL pointer if there is no path
> left.
>
> Fixes: 75c10e732724 ("nvme-multipath: round-robin I/O policy")
> Cc: Hannes Reinecke <hare@suse.de>
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
> ---
> v2:
> - moved NULL test into the if conditional statement
> - added Fixes tag
>
> drivers/nvme/host/multipath.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/multipath.c b/drivers/nvme/host/multipath.c
> index 9ac762b28811..282b7a4ea9a9 100644
> --- a/drivers/nvme/host/multipath.c
> +++ b/drivers/nvme/host/multipath.c
> @@ -221,7 +221,7 @@ static struct nvme_ns *nvme_round_robin_path(struct nvme_ns_head *head,
> }
>
> for (ns = nvme_next_ns(head, old);
> - ns != old;
> + ns && ns != old;
nvme_round_robin_path just be called when !"old".
nvme_next_ns should not return NULL when !"old".
It seems unnecessary to add checking "ns".
Is there a bug that "old" in not in "head" list?
If yes, we should fix it.
> ns = nvme_next_ns(head, ns)) {
> if (nvme_path_is_disabled(ns))
> continue;
>
next prev parent reply other threads:[~2021-01-28 1:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 10:30 [PATCH v2] nvme-multipath: Early exit if no path is available Daniel Wagner
2021-01-27 10:34 ` Hannes Reinecke
2021-01-27 16:49 ` Christoph Hellwig
2021-01-28 1:31 ` Chao Leng [this message]
2021-01-28 7:58 ` Daniel Wagner
2021-01-28 9:18 ` Chao Leng
2021-01-28 9:23 ` Hannes Reinecke
2021-01-29 1:18 ` Chao Leng
2021-01-28 9:40 ` Daniel Wagner
2021-01-29 1:23 ` Chao Leng
2021-01-29 1:42 ` Sagi Grimberg
2021-01-29 3:07 ` Chao Leng
2021-01-29 3:30 ` Sagi Grimberg
2021-01-29 3:36 ` Chao Leng
2021-01-29 7:06 ` Hannes Reinecke
[not found] ` <81b22bbf-4dd3-6161-e63a-9699690a4e4f@huawei.com>
[not found] ` <715dd943-0587-be08-2840-e0948cf0bc62@suse.de>
[not found] ` <eb131d8f-f009-42e7-105d-58b84060f0dd@huawei.com>
[not found] ` <ac019690-7f02-d28c-ed58-bfc8c1d48879@suse.de>
2021-02-01 2:16 ` Chao Leng
2021-02-01 7:29 ` Hannes Reinecke
2021-02-01 8:47 ` Chao Leng
2021-02-01 8:57 ` Hannes Reinecke
2021-02-01 9:40 ` Chao Leng
2021-02-01 10:45 ` Hannes Reinecke
2021-02-02 1:12 ` Chao Leng
2021-01-28 1:36 ` Chao Leng
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=db9baae0-547c-7ff4-8b2c-0b95f14be67c@huawei.com \
--to=lengchao@huawei.com \
--cc=axboe@fb.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).