From: David Sterba <dsterba@suse.cz>
To: Jeff Layton <jlayton@kernel.org>
Cc: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>,
Chuck Lever <cel@kernel.org>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] btrfs: fix FMODE_NOCMTIME handling in btrfs
Date: Mon, 9 Nov 2026 17:10:19 +0100 [thread overview]
Message-ID: <20261109161019.GC4186782@twin.jikos.cz> (raw)
In-Reply-To: <20261105-delegts-btrfs-v1-0-a42a2b93cdc2@kernel.org>
On Thu, Nov 05, 2026 at 03:07:41PM -0500, Jeff Layton wrote:
> I tested the delegated timestamp support in nfsd recently. That support
> relies heavily on FMODE_NOCMTIME, and I found several places where btrfs
> didn't handle that flag properly. This series seems to fix them for me.
> I tested mostly with the git regression testsuite, because it is very
> sensitive to subtle bugs in timestamp handling.
>
> Please consider for v7.5.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> Jeff Layton (4):
> btrfs: honor FMODE_NOCMTIME in btrfs_write_check()
> btrfs: honor FMODE_NOCMTIME when punching holes
> btrfs: honor FMODE_NOCMTIME in fallocate
> btrfs: honor FMODE_NOCMTIME when cloning
There's a comment from sashiko for patch 4 regarding the unconditional
i_version update but this is mentioned in patch 3 as intentional. I
can't tell if it's a problem, it seems more like a suggestion for
cleanup. I'll add the series to for-next, please check if the question
is valid. Thanks.
next prev parent reply other threads:[~2026-11-09 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 20:07 Jeff Layton
2026-11-05 20:07 ` [PATCH 1/4] btrfs: honor FMODE_NOCMTIME in btrfs_write_check() Jeff Layton
2026-11-05 20:07 ` [PATCH 2/4] btrfs: honor FMODE_NOCMTIME when punching holes Jeff Layton
2026-11-05 20:07 ` [PATCH 3/4] btrfs: honor FMODE_NOCMTIME in fallocate Jeff Layton
2026-11-05 20:07 ` [PATCH 4/4] btrfs: honor FMODE_NOCMTIME when cloning Jeff Layton
2026-11-09 16:10 ` David Sterba [this message]
2026-11-09 16:48 ` [PATCH 0/4] btrfs: fix FMODE_NOCMTIME handling in btrfs Jeff Layton
2026-11-09 18:16 ` David Sterba
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=20261109161019.GC4186782@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=cel@kernel.org \
--cc=dsterba@suse.com \
--cc=jlayton@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®