From: Filipe Manana <fdmanana@gmail.com>
To: dsterba@suse.cz, Omar Sandoval <osandov@osandov.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
kernel-team@fb.com
Subject: Re: [PATCH v2 1/4] btrfs-progs: receive: remove commented out transid checks
Date: Wed, 24 Jul 2019 13:10:27 +0100 [thread overview]
Message-ID: <CAL3q7H6Q37XOxn3qkMM-XMW7m+HcVx55AhpZfeogKzaA1AfHhQ@mail.gmail.com> (raw)
In-Reply-To: <20190724112250.GK2868@twin.jikos.cz>
On Wed, Jul 24, 2019 at 12:23 PM David Sterba <dsterba@suse.cz> wrote:
>
> On Mon, Jul 22, 2019 at 12:15:02PM -0700, Omar Sandoval wrote:
> > From: Omar Sandoval <osandov@fb.com>
> >
> > The checks for a subvolume being modified after it was received have
> > been commented out since they were added back in commit f1c24cd80dfd
> > ("Btrfs-progs: add btrfs send/receive commands"). Let's just get rid of
> > the noise.
> >
> > Signed-off-by: Omar Sandoval <osandov@fb.com>
> > ---
> > cmds/receive.c | 25 -------------------------
> > 1 file changed, 25 deletions(-)
> >
> > diff --git a/cmds/receive.c b/cmds/receive.c
> > index b97850a7..830ed082 100644
> > --- a/cmds/receive.c
> > +++ b/cmds/receive.c
> > @@ -344,15 +344,6 @@ static int process_snapshot(const char *path, const u8 *uuid, u64 ctransid,
> > parent_subvol->path[sub_len - root_len - 1] = '\0';
> > }
> > }
> > - /*if (rs_args.ctransid > rs_args.rtransid) {
>
> This looks like a (missing) sanity check, don't we want it?
Un-commenting that will cause receive to fail if we deduplicate into
readonly subvolumes and snaphosts and then use them for send
operations, breaking existing use cases.
--
Filipe David Manana,
“Whether you think you can, or you think you can't — you're right.”
next prev parent reply other threads:[~2019-07-24 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 19:15 [PATCH v2 0/4] btrfs-progs: fix clone from wrong subvolume Omar Sandoval
2019-07-22 19:15 ` [PATCH v2 1/4] btrfs-progs: receive: remove commented out transid checks Omar Sandoval
2019-07-24 11:22 ` David Sterba
2019-07-24 12:10 ` Filipe Manana [this message]
2019-07-22 19:15 ` [PATCH v2 2/4] btrfs-progs: receive: get rid of unnecessary strdup() Omar Sandoval
2019-07-22 19:15 ` [PATCH v2 3/4] btrfs-progs: receive: don't lookup clone root for received subvolume Omar Sandoval
2019-07-23 11:19 ` Filipe Manana
2020-02-24 14:53 ` Filipe Manana
2020-03-11 8:03 ` Omar Sandoval
2019-07-22 19:15 ` [PATCH v2 4/4] btrfs-progs: tests: add test for receiving clone from duplicate subvolume Omar Sandoval
2019-07-23 11:21 ` Filipe Manana
2019-09-04 20:35 ` [PATCH v2 0/4] btrfs-progs: fix clone from wrong subvolume Omar Sandoval
2019-10-10 7:06 ` Qu Wenruo
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=CAL3q7H6Q37XOxn3qkMM-XMW7m+HcVx55AhpZfeogKzaA1AfHhQ@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=dsterba@suse.cz \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.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;
as well as URLs for NNTP newsgroup(s).