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>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for Linux 6.0
Date: Mon, 22 Aug 2022 17:40:18 +0000 [thread overview]
Message-ID: <b3717e756e8360d0f8ccb70a9b13b4cd9d503a8d.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit 3fa5cbdc44de190f2c5605ba7db015ae0d26f668:
NFS: Improve readpage/writepage tracing (2022-08-09 14:11:34 -0400)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.20-2
for you to fetch changes up to ed06fce0b034b2e25bd93430f5c4cbb28036cc1a:
SUNRPC: RPC level errors should set task->tk_rpc_status (2022-08-19 20:32:05 -0400)
Thanks,
Trond
----------------------------------------------------------------
NFS client bugfixes for Linux 6.0
Highlights include:
Stable fixes
- NFS: Fix another fsync() issue after a server reboot
Bugfixes
- NFS: unlink/rmdir shouldn't call d_delete() twice on ENOENT
- NFS: Fix missing unlock in nfs_unlink()
- Add sanity checking of the file type used by __nfs42_ssc_open
- Fix a case where we're failing to set task->tk_rpc_status
Cleanups
- Remove the flag NFS_CONTEXT_RESEND_WRITES that got obsoleted by the
fsync() fix
----------------------------------------------------------------
NeilBrown (1):
NFS: unlink/rmdir shouldn't call d_delete() twice on ENOENT
Olga Kornievskaia (1):
NFSv4.2 fix problems with __nfs42_ssc_open
Sun Ke (1):
NFS: Fix missing unlock in nfs_unlink()
Trond Myklebust (4):
NFS: Fix another fsync() issue after a server reboot
NFS: Remove a bogus flag setting in pnfs_write_done_resend_to_mds
NFS: Cleanup to remove unused flag NFS_CONTEXT_RESEND_WRITES
SUNRPC: RPC level errors should set task->tk_rpc_status
fs/nfs/dir.c | 7 +++++--
fs/nfs/file.c | 15 ++++++---------
fs/nfs/inode.c | 1 +
fs/nfs/nfs4file.c | 6 ++++++
fs/nfs/pnfs.c | 1 -
fs/nfs/write.c | 6 ++++--
include/linux/nfs_fs.h | 2 +-
net/sunrpc/clnt.c | 2 +-
8 files changed, 24 insertions(+), 16 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2022-08-22 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 17:40 Trond Myklebust [this message]
2022-08-22 18:48 ` [GIT PULL] Please pull NFS client bugfixes for Linux 6.0 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=b3717e756e8360d0f8ccb70a9b13b4cd9d503a8d.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.