From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"aksteffen@meta.com" <aksteffen@meta.com>,
"jdq@meta.com" <jdq@meta.com>
Subject: [GIT PULL] Please pull a NFS client bugfix for Linux 6.17
Date: Fri, 22 Aug 2025 00:57:38 +0000 [thread overview]
Message-ID: <b72bf6be6869a8540051bdc6d93f59bbac50d3ea.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:
Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.17-2
for you to fetch changes up to 76d2e3890fb169168c73f2e4f8375c7cc24a765e:
NFS: Fix a race when updating an existing write (2025-08-19 11:16:02 -0700)
----------------------------------------------------------------
NFS client bugfix for Linux 6.17
Stable fixes:
- NFS: Fix a data corrupting race when updating an existing write
----------------------------------------------------------------
Trond Myklebust (1):
NFS: Fix a race when updating an existing write
fs/nfs/pagelist.c | 9 +++++----
fs/nfs/write.c | 29 ++++++++++-------------------
include/linux/nfs_page.h | 1 +
3 files changed, 16 insertions(+), 23 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
next reply other threads:[~2025-08-22 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 0:57 Trond Myklebust [this message]
2025-08-22 13:36 ` [GIT PULL] Please pull a NFS client bugfix for Linux 6.17 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=b72bf6be6869a8540051bdc6d93f59bbac50d3ea.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=aksteffen@meta.com \
--cc=jdq@meta.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.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