From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs-progs: Correctly open filesystem on image file
Date: Thu, 16 May 2019 21:41:04 +0800 [thread overview]
Message-ID: <e7a99dd5-5107-5da9-df95-6ad43bf8ad7e@gmx.com> (raw)
In-Reply-To: <20190516131250.26621-1-nborisov@suse.com>
On 2019/5/16 下午9:12, Nikolay Borisov wrote:
> When btrfs' 'filesystem' subcommand is passed path to an image file it
> currently fails since the code expects the image file is going to be
> recognised by libblkid (called from btrfs_scan_devices()). This is not
> the case since libblkid only scan well-known locations under /dev.
>
> Fix this by explicitly calling open_ctree which will correctly open
> the image and add it to the correct btrfs_fs_devices struct. This allows
> subsequent cmd_filesystem_show logic to correctly show requested
> information.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
> cmds-filesystem.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/cmds-filesystem.c b/cmds-filesystem.c
> index b8beec13f0e5..f55ce9b4ab85 100644
> --- a/cmds-filesystem.c
> +++ b/cmds-filesystem.c
> @@ -771,7 +771,18 @@ static int cmd_filesystem_show(int argc, char **argv)
> goto out;
>
> devs_only:
> - ret = btrfs_scan_devices();
> + if (type == BTRFS_ARG_REG) {
> + /*
> + * We don't close the fs_info because it will free the device,
> + * this is not a long-running process so it's fine
> + */
The comment makes sense, but I'm pretty sure we still prefer to clean it up.
Just something like:
struct btrfs_root *root = NULL;
root = open_ctree();
if (root)
ret = 0;
else
ret = 1;
close_ctree(root);
Despite that, I think the patch looks good to me.
Thanks,
Qu
> + if (open_ctree(search, btrfs_sb_offset(0), 0))
> + ret = 0;
> + else
> + ret = 1;
> + } else {
> + ret = btrfs_scan_devices();
> + }
>
> if (ret) {
> error("blkid device scan returned %d", ret);
>
next prev parent reply other threads:[~2019-05-16 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 13:12 [PATCH 1/2] btrfs-progs: Correctly open filesystem on image file Nikolay Borisov
2019-05-16 13:12 ` [PATCH 2/2] btrfs-progs: tests: Test fs on image files is correctly recognised Nikolay Borisov
2019-06-05 16:14 ` David Sterba
2019-05-16 13:41 ` Qu Wenruo [this message]
2019-05-16 13:45 ` [PATCH 1/2] btrfs-progs: Correctly open filesystem on image file Nikolay Borisov
2019-05-16 13:54 ` Qu Wenruo
2019-05-16 14:01 ` Nikolay Borisov
2019-05-16 14:10 ` Qu Wenruo
2019-06-05 16:20 ` 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=e7a99dd5-5107-5da9-df95-6ad43bf8ad7e@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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