All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: anna@kernel.org
Subject: [GIT PULL] Please Pull NFS Client Bugfixes for Linux 6.16-rc5
Date: Tue,  1 Jul 2025 16:33:45 -0400	[thread overview]
Message-ID: <20250701203345.781391-1-anna@kernel.org> (raw)

Hi Linus,

The following changes since commit 86731a2a651e58953fc949573895f2fa6d456841:

  Linux 6.16-rc3 (2025-06-22 13:30:08 -0700)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-6.16-2

for you to fetch changes up to 38074de35b015df5623f524d6f2b49a0cd395c40:

  NFSv4/flexfiles: Fix handling of NFS level errors in I/O (2025-06-26 13:46:44 -0400)

----------------------------------------------------------------
NFS Client Bugfixes for Linux 6.16

* Fix loop in GSS sequence number cache
* Clean up /proc/net/rpc/nfs if nfs_fs_proc_net_init() fails
* Fix a race to wake on NFS_LAYOUT_DRAIN
* Fix handling of NFS level errors in I/O

Thanks,
Anna

----------------------------------------------------------------
Benjamin Coddington (1):
      NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN

Kuniyuki Iwashima (1):
      nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails.

Nikhil Jha (1):
      sunrpc: fix loop in gss seqno cache

Trond Myklebust (1):
      NFSv4/flexfiles: Fix handling of NFS level errors in I/O

 fs/nfs/flexfilelayout/flexfilelayout.c | 118 +++++++++++++++++++++++----------
 fs/nfs/inode.c                         |  17 ++++-
 fs/nfs/pnfs.c                          |   4 +-
 net/sunrpc/auth_gss/auth_gss.c         |   2 +-
 4 files changed, 102 insertions(+), 39 deletions(-)

             reply	other threads:[~2025-07-01 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 20:33 Anna Schumaker [this message]
2025-07-02 17:06 ` [GIT PULL] Please Pull NFS Client Bugfixes for Linux 6.16-rc5 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=20250701203345.781391-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 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.