From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: anna@kernel.org
Subject: [GIT PULL] NFS Client Bugfixes for Linux 6.6
Date: Mon, 18 Sep 2023 13:51:40 -0400 [thread overview]
Message-ID: <20230918175140.261140-1-anna@kernel.org> (raw)
Hi Linus,
The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-6.6-2
for you to fetch changes up to 993b5662f302628db4eb358d69b2720c88cbfaf0:
SUNRPC: Silence compiler complaints about tautological comparisons (2023-09-15 15:50:39 -0400)
----------------------------------------------------------------
NFS Client Bugfixes for Linux 6.6
Bugfixes:
* Various O_DIRECT related fixes from Trond
* Error handling
* Locking issues
* Use the correct commit infor for joining page groups
* Fixes for rescheduling IO
* Sunrpc bad verifier fixes
* Report EINVAL errors from connect()
* Revalidate creds that the server has rejected
* Revert "SUNRPC: Fail faster on bad verifier"
* Fix pNFS session trunking when MDS=DS
* Fix zero-value filehandles for post-open getattr operations
* Fix compiler warning about tautological comparisons
* Revert "SUNRPC: clean up integer overflow check" before Trond's fix
----------------------------------------------------------------
Anna Schumaker (1):
Revert "SUNRPC: clean up integer overflow check"
Olga Kornievskaia (2):
NFSv4.1: fix pnfs MDS=DS session trunking
NFSv4.1: fix zero value filehandle in post open getattr
Trond Myklebust (9):
NFS: Fix error handling for O_DIRECT write scheduling
NFS: Fix O_DIRECT locking issues
NFS: More O_DIRECT accounting fixes for error paths
NFS: Use the correct commit info in nfs_join_page_group()
NFS: More fixes for nfs_direct_write_reschedule_io()
NFS/pNFS: Report EINVAL errors from connect() to the server
SUNRPC: Mark the cred for revalidation if the server rejects it
Revert "SUNRPC: Fail faster on bad verifier"
SUNRPC: Silence compiler complaints about tautological comparisons
fs/nfs/direct.c | 134 +++++++++++++++++++++++----------
fs/nfs/flexfilelayout/flexfilelayout.c | 1 +
fs/nfs/nfs4client.c | 6 +-
fs/nfs/nfs4proc.c | 6 +-
fs/nfs/write.c | 23 +++---
include/linux/nfs_fs_sb.h | 1 +
include/linux/nfs_page.h | 4 +-
include/linux/sunrpc/xdr.h | 4 +-
net/sunrpc/clnt.c | 14 ++--
9 files changed, 132 insertions(+), 61 deletions(-)
next reply other threads:[~2023-09-18 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 17:51 Anna Schumaker [this message]
2023-09-18 20:20 ` [GIT PULL] NFS Client Bugfixes for Linux 6.6 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=20230918175140.261140-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