From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Wang Shilong <wangshilong1991@gmail.com>, linux-btrfs@vger.kernel.org
Cc: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Subject: Re: [PATCH] Btrfs-progs: avoid using btrfs internal subvolume path to send
Date: Fri, 29 Nov 2013 16:19:21 +0100 [thread overview]
Message-ID: <5298B079.2020907@giantdisaster.de> (raw)
In-Reply-To: <1385734989-8839-1-git-send-email-wangshilong1991@gmail.com>
On Fri, 29 Nov 2013 22:23:09 +0800, Wang Shilong wrote:
> From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
>
> Steps to reproduce:
> # mkfs.btrfs -f /dev/sda
> # mount /dev/sda /mnt
> # btrfs subvolume create /mnt/foo
> # umount /mnt
> # mount -o subvol=foo /dev/sda /mnt
> # btrfs sub snapshot -r /mnt /mnt/snap
> # btrfs send /mnt/snap > /dev/null
>
> We will fail to send '/mnt/snap',this is because btrfs send try to
> open '/mnt/snap' by btrfs internal subvolume path 'foo/snap' rather
> than relative path based on mounted point, this will return us 'no
> such file or directory',this is not right, fix it.
>
> Reported-by: Thomas Scheiblauer <tom@sharkbay.at>
> Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
> ---
> cmds-send.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/cmds-send.c b/cmds-send.c
> index 53e9a53..b3dde83 100644
> --- a/cmds-send.c
> +++ b/cmds-send.c
> @@ -283,7 +283,7 @@ out:
> }
>
> static int do_send(struct btrfs_send *send, u64 root_id, u64 parent_root_id,
> - int is_first_subvol, int is_last_subvol)
> + int is_first_subvol, int is_last_subvol, char *subvol)
> {
> int ret;
> pthread_t t_read;
> @@ -303,10 +303,10 @@ static int do_send(struct btrfs_send *send, u64 root_id, u64 parent_root_id,
> goto out;
> }
>
> - subvol_fd = openat(send->mnt_fd, si->path, O_RDONLY | O_NOATIME);
> + subvol_fd = openat(send->mnt_fd, subvol, O_RDONLY | O_NOATIME);
> if (subvol_fd < 0) {
> ret = -errno;
> - fprintf(stderr, "ERROR: open %s failed. %s\n", si->path,
> + fprintf(stderr, "ERROR: open %s failed. %s\n", subvol,
> strerror(-ret));
> goto out;
> }
> @@ -701,7 +701,7 @@ int cmd_send(int argc, char **argv)
> is_last_subvol = 1;
> }
> ret = do_send(&send, root_id, parent_root_id,
> - is_first_subvol, is_last_subvol);
> + is_first_subvol, is_last_subvol, subvol);
> if (ret < 0)
> goto out;
>
>
You've removed that the subvol_info si is used in do_send().
Then you can remove all the subvol_info si code:
struct subvol_info *si;
...
si = subvol_uuid_search(&send->sus, root_id, NULL, 0, NULL,
subvol_search_by_root_id);
if (!si) {
ret = -ENOENT;
fprintf(stderr, "ERROR: could not find subvol info for
%llu",
root_id);
goto out;
}
...
if (si) {
free(si->path);
free(si);
}
prev parent reply other threads:[~2013-11-29 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 14:23 [PATCH] Btrfs-progs: avoid using btrfs internal subvolume path to send Wang Shilong
2013-11-29 15:19 ` Stefan Behrens [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=5298B079.2020907@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@gmail.com \
--cc=wangsl.fnst@cn.fujitsu.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 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.