From: Su Yue <l@damenly.su>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: [PATCH RFC 3/3] btrfs: use latest_bdev in btrfs_show_devname
Date: Fri, 20 Aug 2021 15:31:11 +0800 [thread overview]
Message-ID: <1r6ofu54.fsf@damenly.su> (raw)
In-Reply-To: <9a06b04b9003f86c3300e497b35b0ef0310c84c0.1629396187.git.anand.jain@oracle.com>
On Fri 20 Aug 2021 at 02:18, Anand Jain <anand.jain@oracle.com>
wrote:
> latest_bdev is updated according to the changes to the device
> list.
> That means we could use the latest_bdev to show the device name
> in
> /proc/self/mounts. So this patch makes that change.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
>
> RFC because
> 1. latest_bdev might not be the lowest devid but, we showed
> the lowest devid in /proc/self/mount.
> 2. The device's path is not shown now but, previously we did.
> So does these break ABI? Maybe yes for 2 howabout for 1 above?
>
Mabybe a naive question but I have no time to dive into btrfs code
recently. If a device which has highest devid was replaced, will
the
new device be the fs_devices->latest_bdev instead of the existing
older
one?
Thanks.
--
Su
> fs/btrfs/super.c | 25 +++----------------------
> 1 file changed, 3 insertions(+), 22 deletions(-)
>
> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> index 1f9dd1a4faa3..4ad3fe174c41 100644
> --- a/fs/btrfs/super.c
> +++ b/fs/btrfs/super.c
> @@ -2464,30 +2464,11 @@ static int btrfs_unfreeze(struct
> super_block *sb)
> static int btrfs_show_devname(struct seq_file *m, struct dentry
> *root)
> {
> struct btrfs_fs_info *fs_info = btrfs_sb(root->d_sb);
> - struct btrfs_device *dev, *first_dev = NULL;
> + char name[BDEVNAME_SIZE];
>
> - /*
> - * Lightweight locking of the devices. We should not need
> - * device_list_mutex here as we only read the device data and
> the list
> - * is protected by RCU. Even if a device is deleted during
> the list
> - * traversals, we'll get valid data, the freeing callback will
> wait at
> - * least until the rcu_read_unlock.
> - */
> - rcu_read_lock();
> - list_for_each_entry_rcu(dev, &fs_info->fs_devices->devices,
> dev_list) {
> - if (test_bit(BTRFS_DEV_STATE_MISSING, &dev->dev_state))
> - continue;
> - if (!dev->name)
> - continue;
> - if (!first_dev || dev->devid < first_dev->devid)
> - first_dev = dev;
> - }
> + seq_escape(m, bdevname(fs_info->fs_devices->latest_bdev,
> name),
> + " \t\n\\");
>
> - if (first_dev)
> - seq_escape(m, rcu_str_deref(first_dev->name), " \t\n\\");
> - else
> - WARN_ON(1);
> - rcu_read_unlock();
> return 0;
> }
next prev parent reply other threads:[~2021-08-20 7:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 18:18 [PATCH 0/3] btrf_show_devname related fixes Anand Jain
2021-08-19 18:18 ` [PATCH 1/3] btrfs: fix comment about the btrfs_show_devname Anand Jain
2021-08-19 18:18 ` [PATCH RFC 2/3] btrfs: consolidate device_list_mutex in prepare_sprout to its parent Anand Jain
2021-08-20 7:51 ` Su Yue
2021-08-20 8:53 ` Anand Jain
2021-08-21 14:57 ` Su Yue
2021-08-21 15:00 ` Su Yue
2021-08-23 10:34 ` Anand Jain
2021-08-23 10:54 ` Anand Jain
2021-08-23 12:20 ` David Sterba
2021-08-19 18:18 ` [PATCH RFC 3/3] btrfs: use latest_bdev in btrfs_show_devname Anand Jain
2021-08-20 7:31 ` Su Yue [this message]
2021-08-20 9:13 ` Anand Jain
2021-08-20 10:57 ` David Sterba
2021-08-20 11:03 ` Anand Jain
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=1r6ofu54.fsf@damenly.su \
--to=l@damenly.su \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).