mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff Layton <jlayton@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-nfs@vger.kernel.org>
Subject: [GIT PULL] NFSD fixes for v6.17-rc
Date: Mon, 11 Aug 2025 10:13:24 -0400	[thread overview]
Message-ID: <20250811141324.6094-1-cel@kernel.org> (raw)

The following changes since commit e339967eecf1305557f7c697e1bc10b5cc495454:

  nfsd: Drop dprintk in blocklayout xdr functions (2025-07-14 12:46:50 -0400)

are available in the Git repository at:

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

for you to fetch changes up to bee47cb026e762841f3faece47b51f985e215edb:

  sunrpc: fix handling of server side tls alerts (2025-08-06 09:57:50 -0400)

----------------------------------------------------------------
nfsd-6.17 fixes:

- A correctness fix for delegated timestamps
- Address an NFSD shutdown hang when LOCALIO is in use
- Prevent a remotely exploitable crasher when TLS is in use

These arrived too late to be included in the initial nfsd-6.17
pull request.

----------------------------------------------------------------
Jeff Layton (1):
      nfsd: don't set the ctime on delegated atime updates

NeilBrown (1):
      nfsd: avoid ref leak in nfsd_open_local_fh()

Olga Kornievskaia (1):
      sunrpc: fix handling of server side tls alerts

 fs/nfsd/localio.c    |  5 +++--
 fs/nfsd/vfs.c        | 10 +++++++++-
 net/sunrpc/svcsock.c | 43 +++++++++++++++++++++++++++++++++++--------
 3 files changed, 47 insertions(+), 11 deletions(-)

             reply	other threads:[~2025-08-11 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 14:13 Chuck Lever [this message]
2025-08-12  4:00 ` 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=20250811141324.6094-1-cel@kernel.org \
    --to=cel@kernel.org \
    --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

all inboxes | Powered by JetHome®