Linux-NFS Archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jeff Layton <jlayton@kernel.org>
Subject: [GIT PULL] first round of NFSD fixes for v6.9
Date: Thu, 28 Mar 2024 14:25:29 -0400	[thread overview]
Message-ID: <ZgW2GVcXbJaPlT8z@tissot.1015granger.net> (raw)

Hi Linus-

The following changes since commit 9b350d3e349f2c4ba4e046001446d533471844a7:

  NFSD: Clean up nfsd4_encode_replay() (2024-03-09 13:57:50 -0500)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.9-1

for you to fetch changes up to 99dc2ef0397d082b63404c01cf841cf80f1418dc:

  NFSD: CREATE_SESSION must never cache NFS4ERR_DELAY replies (2024-03-27 13:19:47 -0400)

----------------------------------------------------------------
nfsd-6.9 fixes:
- Address three recently introduced regressions

----------------------------------------------------------------
Chuck Lever (2):
      SUNRPC: Revert 561141dd494382217bace4d1a51d08168420eace
      NFSD: CREATE_SESSION must never cache NFS4ERR_DELAY replies

Jan Kara (1):
      nfsd: Fix error cleanup path in nfsd_rename()

 fs/nfsd/nfs4state.c                   | 36 +++++++++++++++++++++++++-----------
 fs/nfsd/vfs.c                         |  3 ++-
 net/sunrpc/auth_gss/gss_krb5_crypto.c | 14 ++++++++------
 3 files changed, 35 insertions(+), 18 deletions(-)

-- 
Chuck Lever

             reply	other threads:[~2024-03-28 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 18:25 Chuck Lever [this message]
2024-03-29  0:19 ` [GIT PULL] first round of NFSD fixes for v6.9 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=ZgW2GVcXbJaPlT8z@tissot.1015granger.net \
    --to=chuck.lever@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).