All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff Layton <jlayton@kernel.org>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] 3rd round of NFSD fixes for v6.9-rc
Date: Mon, 15 Apr 2024 17:03:21 -0400	[thread overview]
Message-ID: <Zh2WGRLG3mA92OxN@tissot.1015granger.net> (raw)

The following changes since commit 10396f4df8b75ff6ab0aa2cd74296565466f2c8d:

  nfsd: hold a lighter-weight client reference over CB_RECALL_ANY (2024-04-05 14:05:35 -0400)

are available in the Git repository at:

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

for you to fetch changes up to f488138b526715c6d2568d7329c4477911be4210:

  NFSD: fix endianness issue in nfsd4_encode_fattr4 (2024-04-11 09:21:06 -0400)

----------------------------------------------------------------
nfsd-6.9 fixes:
- Fix a potential tracepoint crash
- Fix NFSv4 GETATTR on big-endian platforms

----------------------------------------------------------------
Steven Rostedt (Google) (1):
      SUNRPC: Fix rpcgss_context trace event acceptor field

Vasily Gorbik (1):
      NFSD: fix endianness issue in nfsd4_encode_fattr4

 fs/nfsd/nfs4xdr.c             | 47 +++++++++++++++++++++++------------------------
 include/trace/events/rpcgss.h |  4 ++--
 2 files changed, 25 insertions(+), 26 deletions(-)

-- 
Chuck Lever

             reply	other threads:[~2024-04-15 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 21:03 Chuck Lever [this message]
2024-04-15 22:13 ` [GIT PULL] 3rd round of NFSD fixes for v6.9-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=Zh2WGRLG3mA92OxN@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 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.