From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com,
Chris Murphy <chris@colorremedies.com>
Subject: Re: [PATCH][v2] btrfs: don't show full path of bind mounts in subvol=
Date: Wed, 29 Jul 2020 20:39:29 +0200 [thread overview]
Message-ID: <20200729183929.GC3703@twin.jikos.cz> (raw)
In-Reply-To: <20200722151246.3789-1-josef@toxicpanda.com>
On Wed, Jul 22, 2020 at 11:12:46AM -0400, Josef Bacik wrote:
> Chris Murphy reported a problem where rpm ostree will bind mount a bunch
> of things for whatever voodoo it's doing. But when it does this
> /proc/mounts shows something like
>
> /dev/mapper/vg0-lv0 /mnt/test btrfs rw,seclabel,relatime,ssd,space_cache,subvolid=256,subvol=/foo 0 0
> /dev/mapper/vg0-lv0 /mnt/test/baz btrfs rw,seclabel,relatime,ssd,space_cache,subvolid=256,subvol=/foo/bar 0 0
>
> Despite subvolid=256 being subvol=/roo. This is because we're just
> spitting out the dentry of the mount point, which in the case of bind
> mounts is the source path for the mountpoint. Instead we should spit
> out the path to the actual subvol. Fix this by looking up the name for
> the subvolid we have mounted. With this fix the same test looks like
> this
>
> /dev/mapper/vg0-lv0 /mnt/test btrfs rw,seclabel,relatime,ssd,space_cache,subvolid=256,subvol=/foo 0 0
> /dev/mapper/vg0-lv0 /mnt/test/baz btrfs rw,seclabel,relatime,ssd,space_cache,subvolid=256,subvol=/foo 0 0
>
> Reported-by: Chris Murphy <chris@colorremedies.com>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> ---
> v1->v2:
> - Dropped the RFC.
> - Added examples of before and after.
>
> fs/btrfs/super.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> index 58f890f73650..0e1647c08610 100644
> --- a/fs/btrfs/super.c
> +++ b/fs/btrfs/super.c
> @@ -1367,6 +1367,7 @@ static int btrfs_show_options(struct seq_file *seq, struct dentry *dentry)
> {
> struct btrfs_fs_info *info = btrfs_sb(dentry->d_sb);
> const char *compress_type;
> + const char *subvol_name;
>
> if (btrfs_test_opt(info, DEGRADED))
> seq_puts(seq, ",degraded");
> @@ -1453,8 +1454,12 @@ static int btrfs_show_options(struct seq_file *seq, struct dentry *dentry)
> seq_puts(seq, ",ref_verify");
> seq_printf(seq, ",subvolid=%llu",
> BTRFS_I(d_inode(dentry))->root->root_key.objectid);
> - seq_puts(seq, ",subvol=");
> - seq_dentry(seq, dentry, " \t\n\\");
> + subvol_name = btrfs_get_subvol_name_from_objectid(info,
> + BTRFS_I(d_inode(dentry))->root->root_key.objectid);
> + if (subvol_name) {
> + seq_printf(seq, ",subvol=%s", subvol_name);
> + kfree(subvol_name);
> + }
Applied with this fixup
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -1476,7 +1476,8 @@ static int btrfs_show_options(struct seq_file *seq, struct dentry *dentry)
subvol_name = btrfs_get_subvol_name_from_objectid(info,
BTRFS_I(d_inode(dentry))->root->root_key.objectid);
if (subvol_name) {
- seq_printf(seq, ",subvol=%s", subvol_name);
+ seq_puts(seq, ",subvol=");
+ seq_escape(seq, subvol_name, " \t\n\\");
kfree(subvol_name);
}
return 0;
and added to misc-next, thanks.
prev parent reply other threads:[~2020-07-29 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 15:12 [PATCH][v2] btrfs: don't show full path of bind mounts in subvol= Josef Bacik
2020-07-29 18:39 ` David Sterba [this message]
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=20200729183929.GC3703@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=chris@colorremedies.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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