All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Leng <lengchao@huawei.com>
To: Hannes Reinecke <hare@suse.de>, Sagi Grimberg <sagi@grimberg.me>,
	"Daniel Wagner" <dwagner@suse.de>
Cc: Jens Axboe <axboe@fb.com>, Keith Busch <kbusch@kernel.org>,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] nvme-multipath: Early exit if no path is available
Date: Fri, 29 Jan 2021 15:45:39 +0800	[thread overview]
Message-ID: <81b22bbf-4dd3-6161-e63a-9699690a4e4f@huawei.com> (raw)
In-Reply-To: <65392653-6b03-9195-f686-5fe4b3290bd2@suse.de>



On 2021/1/29 15:06, Hannes Reinecke wrote:
> On 1/29/21 4:07 AM, Chao Leng wrote:
>>
>>
>> On 2021/1/29 9:42, Sagi Grimberg wrote:
>>>
>>>>> You can't see exactly where it dies but I followed the assembly to
>>>>> nvme_round_robin_path(). Maybe it's not the initial nvme_next_ns(head,
>>>>> old) which returns NULL but nvme_next_ns() is returning NULL eventually
>>>>> (list_next_or_null_rcu()).
>>>> So there is other bug cause nvme_next_ns abormal.
>>>> I review the code about head->list and head->current_path, I find 2 bugs
>>>> may cause the bug:
>>>> First, I already send the patch. see:
>>>> https://lore.kernel.org/linux-nvme/20210128033351.22116-1-lengchao@huawei.com/
>>>> Second, in nvme_ns_remove, list_del_rcu is before
>>>> nvme_mpath_clear_current_path. This may cause "old" is deleted from the
>>>> "head", but still use "old". I'm not sure there's any other
>>>> consideration here, I will check it and try to fix it.
>>>
>>> The reason why we first remove from head->list and only then clear
>>> current_path is because the other way around there is no way
>>> to guarantee that that the ns won't be assigned as current_path
>>> again (because it is in head->list).
>> ok, I see.
>>>
>>> nvme_ns_remove fences continue of deletion of the ns by synchronizing
>>> the srcu such that for sure the current_path clearance is visible.
>> The list will be like this:
>> head->next = ns1;
>> ns1->next = head;
>> old->next = ns1;
> 
> Where does 'old' pointing to?
> 
>> This may cause infinite loop in nvme_round_robin_path.
>> for (ns = nvme_next_ns(head, old);
>>      ns != old;
>>      ns = nvme_next_ns(head, ns))
>> The ns will always be ns1, and then infinite loop.
> 
> No. nvme_next_ns() will return NULL.
If there is just one path(the "old") and the "old" is deleted,
nvme_next_ns() will return NULL.
The list like this:
head->next = head;
old->next = head;
If there is two or more path and the "old" is deleted,
"for" will be infinite loop. because nvme_next_ns() will return
the path which in the list except the "old", check condition will
be true for ever.
For example, there is two path: one is the "old", another is "ns1".
The list like this:
head->next = ns1;
ns1->next = head;
old->next = ns1;
nvme_next_ns(head, old) will return ns1;
Then nvme_next_ns(head, ns1) will return ns1;
And then infinite loop.
> 
> Cheers,
> 
> Hannes

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-01-29  7:45 UTC|newest]

Thread overview: 50+ 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:30 ` Daniel Wagner
2021-01-27 10:34 ` Hannes Reinecke
2021-01-27 10:34   ` Hannes Reinecke
2021-01-27 16:49 ` Christoph Hellwig
2021-01-27 16:49   ` Christoph Hellwig
2021-01-28  1:31 ` Chao Leng
2021-01-28  1:31   ` Chao Leng
2021-01-28  7:58   ` Daniel Wagner
2021-01-28  7:58     ` Daniel Wagner
2021-01-28  9:18     ` Chao Leng
2021-01-28  9:18       ` Chao Leng
2021-01-28  9:23       ` Hannes Reinecke
2021-01-28  9:23         ` Hannes Reinecke
2021-01-29  1:18         ` Chao Leng
2021-01-29  1:18           ` Chao Leng
2021-01-28  9:40       ` Daniel Wagner
2021-01-28  9:40         ` Daniel Wagner
2021-01-29  1:23         ` Chao Leng
2021-01-29  1:23           ` Chao Leng
2021-01-29  1:42           ` Sagi Grimberg
2021-01-29  1:42             ` Sagi Grimberg
2021-01-29  3:07             ` Chao Leng
2021-01-29  3:07               ` Chao Leng
2021-01-29  3:30               ` Sagi Grimberg
2021-01-29  3:30                 ` Sagi Grimberg
2021-01-29  3:36                 ` Chao Leng
2021-01-29  3:36                   ` Chao Leng
2021-01-29  7:06               ` Hannes Reinecke
2021-01-29  7:06                 ` Hannes Reinecke
2021-01-29  7:45                 ` Chao Leng [this message]
2021-01-29  8:33                   ` Hannes Reinecke
2021-01-29  8:46                     ` Chao Leng
2021-01-29  9:20                       ` Hannes Reinecke
2021-02-01  2:16                         ` Chao Leng
2021-02-01  2:16                           ` Chao Leng
2021-02-01  7:29                           ` Hannes Reinecke
2021-02-01  7:29                             ` Hannes Reinecke
2021-02-01  8:47                             ` Chao Leng
2021-02-01  8:47                               ` Chao Leng
2021-02-01  8:57                               ` Hannes Reinecke
2021-02-01  8:57                                 ` Hannes Reinecke
2021-02-01  9:40                                 ` Chao Leng
2021-02-01  9:40                                   ` Chao Leng
2021-02-01 10:45                                   ` Hannes Reinecke
2021-02-01 10:45                                     ` Hannes Reinecke
2021-02-02  1:12                                     ` Chao Leng
2021-02-02  1:12                                       ` Chao Leng
2021-01-28  1:36 ` 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=81b22bbf-4dd3-6161-e63a-9699690a4e4f@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 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.