From: Jeff Layton <jlayton@kernel.org>
To: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>,
Chuck Lever <cel@kernel.org>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: [PATCH 0/4] btrfs: fix FMODE_NOCMTIME handling in btrfs
Date: Thu, 05 Nov 2026 15:07:41 -0500 [thread overview]
Message-ID: <20261105-delegts-btrfs-v1-0-a42a2b93cdc2@kernel.org> (raw)
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
fs/btrfs/btrfs_inode.h | 3 ++-
fs/btrfs/ctree.h | 2 --
fs/btrfs/file.c | 60 +++++++++++++++++++++++++++++++++++---------------
fs/btrfs/file.h | 2 ++
fs/btrfs/inode.c | 13 ++++++-----
fs/btrfs/reflink.c | 9 ++++----
fs/btrfs/relocation.c | 2 +-
7 files changed, 59 insertions(+), 32 deletions(-)
---
base-commit: d692f252c52b8d1b4bc7481554f314df31ed8249
change-id: 20261104-delegts-btrfs-124230048ca7
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2026-11-05 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 20:07 Jeff Layton [this message]
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
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=20261105-delegts-btrfs-v1-0-a42a2b93cdc2@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=dsterba@suse.com \
--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®