All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sidong Yang <realwakka@gmail.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/1] btrfs/339: test receive dump stream for different user
Date: Wed, 3 Dec 2025 11:38:29 +0000	[thread overview]
Message-ID: <aTAhNRFMJMYWkhtO@sidong> (raw)
In-Reply-To: <CAL3q7H5e6R5XzFQTfx9hpxsiaVoQoiXgsqSTRO9GQAhmv+-rng@mail.gmail.com>

On Tue, Dec 02, 2025 at 02:57:19PM +0000, Filipe Manana wrote:
> On Wed, Nov 19, 2025 at 5:30 AM Sidong Yang <realwakka@gmail.com> wrote:
> >
> > Test receive to dump stream file from different user.
> >
> > This is a regression test for the btrfs-progs commit cd933616d485
> > ("btrfs-progs: receive: don't use O_NOATIME to open stream for
> > dumping").
> >
> > Signed-off-by: Sidong Yang <realwakka@gmail.com>
> > ---
> > v2:
> > - forward to $seqres.full rather than -q
> > - use $tmp for stream file
> > ---
> >  tests/btrfs/339     | 40 ++++++++++++++++++++++++++++++++++++++++
> >  tests/btrfs/339.out |  2 ++
> >  2 files changed, 42 insertions(+)
> >  create mode 100755 tests/btrfs/339
> >  create mode 100644 tests/btrfs/339.out
> >
> > diff --git a/tests/btrfs/339 b/tests/btrfs/339
> > new file mode 100755
> > index 00000000..0df24577
> > --- /dev/null
> > +++ b/tests/btrfs/339
> > @@ -0,0 +1,40 @@
> > +#! /bin/bash
> > +# SPDX-License-Identifier: GPL-2.0
> > +# Copyright (c) 2025 Sidong Yang.  All Rights Reserved.
> > +#
> > +# FS QA Test 339
> > +#
> > +# Test btrfs receive dump stream from different user
> > +#
> > +. ./common/preamble
> > +_begin_fstest auto quick send snapshot
> > +
> > +# Override the default cleanup function.
> > +_cleanup()
> > +{
> > +       cd /
> > +       rm -r -f $tmp.*
> > +}
> 
> This does the same as the default _cleanup function, so there's no
> need to have it, just remove it.

I see, Thanks

> 
> > +
> > +. ./common/filter
> > +. ./common/quota
> 
> Why include the quota file? It's not needed, the test doesn't use
> anything from it, just remove it.

I don't need it. Removed.
> 
> > +
> > +_require_scratch
> > +_require_user
> > +
> > +_fixed_by_git_commit btrfs-progs cd933616d485 \
> > +       "btrfs-progs: receive: don't use O_NOATIME to open stream for dumping"
> > +
> > +_scratch_mkfs >> $seqres.full 2>&1 || _fail "mkfs failed"
> > +_scratch_mount
> > +
> > +stream=$tmp.fsv.ss
> > +
> > +$BTRFS_UTIL_PROG subvolume snapshot -r $SCRATCH_MNT $SCRATCH_MNT/snap >> $seqres.full
> 
> Nowadays we use _btrfs, it's shorter and does the same (including the
> stdout redirection):
> 
> _btrfs subvolume snapshot -r $SCRATCH_MNT $SCRATCH_MNT/snap
> 
> > +$BTRFS_UTIL_PROG send -f $stream $SCRATCH_MNT/snap >> $seqres.full 2>&1 || _fail "send failed"
> 
> And here:
> 
> _btrfs send -f $stream $SCRATCH_MNT/snap
> 
> There's no need to:  || _fail "send failed"
> That is generally discouraged in fstests. A failure will just cause a
> mismatch with the golden output and make the test fail.
> 
> But _btrfs already calls _fail and redirects to the .full file anyway.
> 
> Otherwise it looks good, thanks.

Thanks, I'll send a new version right away.

Thanks,
Sidong
> 
> 
> 
> > +chmod a+r $stream
> > +_su $qa_user -c "$BTRFS_UTIL_PROG receive --dump -f $stream" >> $seqres.full
> > +
> > +# success, all done
> > +echo "Silence is golden"
> > +_exit 0
> > diff --git a/tests/btrfs/339.out b/tests/btrfs/339.out
> > new file mode 100644
> > index 00000000..293ea808
> > --- /dev/null
> > +++ b/tests/btrfs/339.out
> > @@ -0,0 +1,2 @@
> > +QA output created by 339
> > +Silence is golden
> > --
> > 2.43.0
> >
> >

      reply	other threads:[~2025-12-03 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  5:28 [PATCH v2 1/1] btrfs/339: test receive dump stream for different user Sidong Yang
2025-12-02 14:57 ` Filipe Manana
2025-12-03 11:38   ` Sidong Yang [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=aTAhNRFMJMYWkhtO@sidong \
    --to=realwakka@gmail.com \
    --cc=fdmanana@kernel.org \
    --cc=fstests@vger.kernel.org \
    --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.