From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: anna@kernel.org
Subject: [GIT PULL] Please Pull NFS Client Bugfixes for Linux 6.18-rc
Date: Fri, 17 Oct 2025 16:44:26 -0400 [thread overview]
Message-ID: <20251017204426.355167-1-anna@kernel.org> (raw)
Hi Linus,
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-6.18-2
for you to fetch changes up to 9bb3baa9d1604cd20f49ae7dac9306b4037a0e7a:
NFS4: Fix state renewals missing after boot (2025-10-13 14:33:00 -0400)
----------------------------------------------------------------
NFS Client Bugfixes for Linux 6.18-rc
Bugfixes:
* Fix for FlexFiles mirror->dss allocation
* Apply delay_retrans to async operations
* Check if suid/sgid is cleared after a write when needed
* Fix setting the state renewal timer for early mounts after a reboot
Thanks,
Anna
----------------------------------------------------------------
Joshua Watt (2):
NFS4: Apply delay_retrans to async operations
NFS4: Fix state renewals missing after boot
Mike Snitzer (1):
NFSv4/flexfiles: fix to allocate mirror->dss before use
Scott Mayhew (1):
NFS: check if suid/sgid was cleared after a write as needed
fs/nfs/flexfilelayout/flexfilelayout.c | 35 ++++++++++++++++++++--------------
fs/nfs/nfs4client.c | 1 +
fs/nfs/nfs4proc.c | 13 +++++++++++++
fs/nfs/write.c | 3 ++-
include/linux/nfs_xdr.h | 1 +
5 files changed, 38 insertions(+), 15 deletions(-)
next reply other threads:[~2025-10-17 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 20:44 Anna Schumaker [this message]
2025-10-18 17:26 ` [GIT PULL] Please Pull NFS Client Bugfixes for Linux 6.18-rc pr-tracker-bot
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=20251017204426.355167-1-anna@kernel.org \
--to=anna@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).