From: Zorro Lang <zlang@kernel.org>
To: Prabhakar Pujeri <prabhakar.pujeri@dell.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>, fstests@vger.kernel.org
Subject: Re: [PATCH] generic/795: add missing _require_scratch check
Date: Thu, 3 Sep 2026 00:59:13 +0800 [thread overview]
Message-ID: <aphTzWxMpDhC7ISV@zlang-mailbox> (raw)
In-Reply-To: <20260902151316.GJ839663@frogsfrogsfrogs>
On Wed, Sep 02, 2026 at 08:13:16AM -0700, Darrick J. Wong wrote:
> On Wed, Sep 02, 2026 at 05:01:39AM +0000, Prabhakar Pujeri wrote:
> > The test runs _scratch_mkfs and _scratch_mount without first requiring a scratch device, so it fails messily instead of skipping when no scratch device is configured.
> >
> > Signed-off-by: Prabhakar Pujeri <prabhakar.pujeri@dell.com>
>
> Looks ok, though if you're going to write more of these patches you
> might want to put them all under a single patchset...
Yes, I've locally merged your 3 patches that add _require_scratch:
btrfs/333: require scratch before checking encoded reads
overlay/081: add missing _require_scratch check
btrfs/273: add missing _require_scratch check
Are you still working on this progress? If so please consider sending them as a
single patch or unified patchset so I don't have to pick them piecemeal.
If there are no more, I'll just merge this one with the other three :)
Thanks,
Zorro
>
> Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
>
> --D
>
> > ---
> > tests/generic/795 | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/tests/generic/795 b/tests/generic/795
> > index fa5474c5..4c0e7bdb 100755
> > --- a/tests/generic/795
> > +++ b/tests/generic/795
> > @@ -27,6 +27,8 @@ _cleanup()
> >
> > . ./common/filter
> >
> > +_require_scratch
> > +
> > fsv_file_size=10000000
> > nproc_enabler=$((4 * LOAD_FACTOR))
> > nproc_reader=$((6 * LOAD_FACTOR))
> > --
> > 2.55.0
> >
> >
prev parent reply other threads:[~2026-09-02 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 5:01 [PATCH] generic/795: add missing _require_scratch check Prabhakar Pujeri
2026-09-02 15:13 ` Darrick J. Wong
2026-09-02 16:59 ` Zorro Lang [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=aphTzWxMpDhC7ISV@zlang-mailbox \
--to=zlang@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=prabhakar.pujeri@dell.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.