From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com, Filipe Manana <fdmanana@gmail.com>
Subject: [PATCH RESEND v2 0/3] btrfs-progs: fix clone from wrong subvolume
Date: Wed, 11 Mar 2020 01:17:08 -0700 [thread overview]
Message-ID: <cover.1583914311.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hi,
This is a resend of [1] from last July fixing a bug when the same
subvolume is received multiple times. It appears that the series got
lost at some point.
The only changes from v2 are adding Filipe's reviewed-bys and removing
the strdup cleanup patch that was already merged. Based on the devel
branch.
Thanks!
1: https://lore.kernel.org/linux-btrfs/cover.1563822638.git.osandov@fb.com/
Omar Sandoval (3):
btrfs-progs: receive: remove commented out transid checks
btrfs-progs: receive: don't lookup clone root for received subvolume
btrfs-progs: tests: add test for receiving clone from duplicate
subvolume
cmds/receive.c | 43 ++++---------------
.../test.sh | 34 +++++++++++++++
2 files changed, 42 insertions(+), 35 deletions(-)
create mode 100755 tests/misc-tests/038-receive-clone-from-current-subvolume/test.sh
--
2.25.1
next reply other threads:[~2020-03-11 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 8:17 Omar Sandoval [this message]
2020-03-11 8:17 ` [PATCH RESEND v2 1/3] btrfs-progs: receive: remove commented out transid checks Omar Sandoval
2020-03-11 15:50 ` Filipe Manana
2020-03-11 8:17 ` [PATCH RESEND v2 2/3] btrfs-progs: receive: don't lookup clone root for received subvolume Omar Sandoval
2020-03-11 8:17 ` [PATCH RESEND v2 3/3] btrfs-progs: tests: add test for receiving clone from duplicate subvolume Omar Sandoval
2020-03-23 20:01 ` 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=cover.1583914311.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=fdmanana@gmail.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.