From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
cel@kernel.org, Zorro Lang <zlang@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fstests: disable generic duperemove tests for NFS and others
Date: Mon, 9 Dec 2024 07:07:17 -0800 [thread overview]
Message-ID: <Z1cHpXAS0S8R6_g4@infradead.org> (raw)
In-Reply-To: <6dc5c09f-e1a2-4296-93d7-b2cda471a73f@oracle.com>
On Mon, Dec 09, 2024 at 10:00:58AM -0500, Chuck Lever wrote:
> 2. How to disable this test on filesystems (like NFS) where duperemove
> is not supported or where the test is not meaningful. The current check
> for the presence of the duperemove executable is IMO inadequate.
I've not looked at dupremove, but the name suggested it's de-duplicating
and thus needs a working FIDEDUPERANGE ioctl. So the test should check
for that using the _require_test_dedupe / _require_scratch_dedupe
helpers. generic/{559,560,561} do that, so something either in these
helpers is probably broken given that NFS rejects remap_file_range
with REMAP_FILE_DEDUP, although a bit of tracing would be useful if
there actually is something broken in NFS or the VFS.
next prev parent reply other threads:[~2024-12-09 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 18:07 [PATCH] fstests: disable generic duperemove tests for NFS and others cel
2024-12-08 20:01 ` Dave Chinner
2024-12-09 13:49 ` Christoph Hellwig
2024-12-09 15:00 ` Chuck Lever
2024-12-09 15:07 ` Christoph Hellwig [this message]
2024-12-09 19:35 ` Chuck Lever
2024-12-09 18:45 ` Zorro Lang
2024-12-09 18:50 ` Chuck Lever
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=Z1cHpXAS0S8R6_g4@infradead.org \
--to=hch@infradead.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.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 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.