Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Su Yue <l@damenly.su>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: update comment for fs_devices::seed_list in btrfs_rm_device
Date: Wed, 18 Aug 2021 14:13:42 +0800	[thread overview]
Message-ID: <a8f575fc-2741-6379-5b89-62353a54cc8f@oracle.com> (raw)
In-Reply-To: <ce1a0cc1-b616-36e3-8c58-4edde5f924cf@oracle.com>



On 18/08/2021 12:25, Anand Jain wrote:
> On 18/08/2021 12:15, Su Yue wrote:
>> Update it since commit 944d3f9fac61 ("btrfs: switch seed device to
>> list api") did conversion from fs_devices::seed to fs_devices::seed_list.
>>
>> Signed-off-by: Su Yue <l@damenly.su>
> 


> Reviewed-by: Anand Jain <anand.jain@oracle.com>

  Ah. No. I have remove my RB...
> 
>> ---
>>   fs/btrfs/volumes.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index 70f94b75f25a..fcc2fede9ffc 100644
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -2203,7 +2203,7 @@ int btrfs_rm_device(struct btrfs_fs_info 
>> *fs_info, const char *device_path,
>>       /*
>>        * In normal cases the cur_devices == fs_devices. But in case
>>        * of deleting a seed device, the cur_devices should point to
>> -     * its own fs_devices listed under the fs_devices->seed.
>> +     * its own fs_devices listed under the fs_devices->seed_list.


fs_devices->seed is correct.

222 struct btrfs_fs_devices {
::
257         struct btrfs_fs_devices *seed;

Thanks, Anand


>>        */
>>       cur_devices = device->fs_devices;
>>       mutex_lock(&fs_devices->device_list_mutex);
>>
> 

  reply	other threads:[~2021-08-18  6:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  4:15 [PATCH] btrfs: update comment for fs_devices::seed_list in btrfs_rm_device Su Yue
2021-08-18  4:25 ` Anand Jain
2021-08-18  6:13   ` Anand Jain [this message]
2021-08-18  6:20     ` Nikolay Borisov
2021-08-18  6:49       ` Anand Jain
2021-08-18  6:28     ` Anand Jain
2021-08-23 12:59 ` David Sterba

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=a8f575fc-2741-6379-5b89-62353a54cc8f@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=l@damenly.su \
    --cc=linux-btrfs@vger.kernel.org \
    /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