From: Jan Prusakowski via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zorro Lang <zlang@redhat.com>
Cc: jaegeuk@kernel.org, Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v1 0/1] generic/018: do not run the test if a compressed filesystem is used
Date: Mon, 30 Jun 2025 21:58:30 +0200 [thread overview]
Message-ID: <CAHwWncjjZdcXDBmKH-Hm8vL2MW_9rHjr6_fPMxwhUAkmjiuNHw@mail.gmail.com> (raw)
In-Reply-To: <20250620142825.hczg4ldsk46delze@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Fri, Jun 20, 2025 at 4:28 PM Zorro Lang <zlang@redhat.com> wrote:
>
> I saw you used _require_no_compress in your patch, but this function only supports
> btrfs checking currently. How do you avoid your test failure on F2FS?
Hi Zorro,
You're right - that patch won't work as I intended. Thanks for taking the time
to review it. We've done some more checks and it looks like our initial
suspicion was wrong and we'll need a kernel fix to address the problems with the
test.
Thanks again!
Jan
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2025-06-30 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 8:29 [f2fs-dev] [PATCH v1 0/1] generic/018: do not run the test if a compressed filesystem is used Jan Prusakowski via Linux-f2fs-devel
2025-06-20 8:29 ` [f2fs-dev] [PATCH v1 1/1] " Jan Prusakowski via Linux-f2fs-devel
2025-06-20 14:28 ` [f2fs-dev] [PATCH v1 0/1] " Zorro Lang via Linux-f2fs-devel
2025-06-30 19:58 ` Jan Prusakowski via Linux-f2fs-devel [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=CAHwWncjjZdcXDBmKH-Hm8vL2MW_9rHjr6_fPMxwhUAkmjiuNHw@mail.gmail.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jprusakowski@google.com \
--cc=zlang@kernel.org \
--cc=zlang@redhat.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).