From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH 0/2] btrfs-progs: fix clone from wrong subvolume
Date: Fri, 19 Jul 2019 22:39:59 -0700 [thread overview]
Message-ID: <cover.1563600688.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hi,
This series is a couple of minor fixes to btrfs receive. Patch 1 fixes a
missing strdup() return value check by getting rid of the strdup().
Patch 2 (the more important one) fixes a receive error when the same
subvolume is received multiple times.
Thanks,
Omar
Omar Sandoval (2):
btrfs-progs: receive: get rid of unnecessary strdup()
btrfs-progs: receive: don't lookup clone root for received subvolume
cmds/receive.c | 41 +++++++++++------------------------------
1 file changed, 11 insertions(+), 30 deletions(-)
--
2.22.0
next reply other threads:[~2019-07-20 5:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 5:39 Omar Sandoval [this message]
2019-07-20 5:40 ` [PATCH 1/2] btrfs-progs: receive: get rid of unnecessary strdup() Omar Sandoval
2019-07-20 5:42 ` Omar Sandoval
2019-07-20 8:34 ` Mike Fleetwood
2019-07-21 3:17 ` Omar Sandoval
2019-07-20 5:40 ` [PATCH 2/2] btrfs-progs: receive: don't lookup clone root for received subvolume Omar Sandoval
2019-07-22 12:16 ` Filipe Manana
2019-07-22 18:20 ` Omar Sandoval
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=cover.1563600688.git.osandov@fb.com \
--to=osandov@osandov.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 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.