public inbox for linux-nfs@vger.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 Updates for Linux 6.1
Date: Wed, 12 Oct 2022 16:40:31 -0400	[thread overview]
Message-ID: <20221012204031.657633-1-anna@kernel.org> (raw)

Hi Linus,

The following changes since commit f76349cf41451c5c42a99f18a9163377e4b364ff:

  Linux 6.0-rc7 (2022-09-25 14:01:02 -0700)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-6.1-1

for you to fetch changes up to b739a5bd9d9f18cc69dced8db128ef7206e000cd:

  NFSv4/flexfiles: Cancel I/O if the layout is recalled or revoked (2022-10-06 09:52:09 -0400)

----------------------------------------------------------------
NFS Client Updates for Linux 6.1

- New Features:
  - Add NFSv4.2 xattr tracepoints
  - Replace xprtiod WQ in rpcrdma
  - Flexfiles cancels I/O on layout recall or revoke

- Bugfixes and Cleanups:
  - Directly use ida_alloc() / ida_free()
  - Don't open-code max_t()
  - Prefer using strscpy over strlcpy
  - Remove unused forward declarations
  - Always return layout states on flexfiles layout return
  - Have LISTXATTR treat NFS4ERR_NOXATTR as an empty reply instead of error
  - Allow more xprtrdma memory allocations to fail without triggering a reclaim
  - Various other xprtrdma clean ups
  - Fix rpc_killall_tasks() races

Thanks,
Anna

----------------------------------------------------------------
Anna Schumaker (4):
      NFSv4.2: Add special handling for LISTXATTR receiving NFS4ERR_NOXATTR
      NFSv4.2: Move TRACE_DEFINE_ENUM(NFS4_CONTENT_*) under CONFIG_NFS_V4_2
      NFSv4.2: Add tracepoints for getxattr, setxattr, and removexattr
      NFSv4.2: Add a tracepoint for listxattr

Bo Liu (2):
      SUNRPC: Directly use ida_alloc()/free()
      NFSv4: Directly use ida_alloc()/free()

Chuck Lever (8):
      SUNRPC: Replace the use of the xprtiod WQ in rpcrdma
      svcrdma: Clean up RPCRDMA_DEF_GFP
      xprtrdma: Clean up synopsis of rpcrdma_req_create()
      xprtrdma: Clean up synopsis of rpcrdma_regbuf_alloc()
      xprtrdma: MR-related memory allocation should be allowed to fail
      xprtrdma: Memory allocation should be allowed to fail during connect
      xprtrdma: Prevent memory allocations from driving a reclaim
      xprtrdma: Fix uninitialized variable

Gaosheng Cui (2):
      NFSv4: remove nfs4_renewd_prepare_shutdown() declaration
      nfs: remove nfs_wait_atomic_killable() and nfs_write_prepare() declaration

Jiangshan Yi (1):
      fs/nfs/pnfs_nfs.c: fix spelling typo and syntax error in comment

Lukas Bulwahn (1):
      NFS: clean up a needless assignment in nfs_file_write()

Trond Myklebust (5):
      NFSv4/pNFS: Always return layout stats on layout return for flexfiles
      SUNRPC: Fix races with rpc_killall_tasks()
      SUNRPC: Add a helper to allow pNFS drivers to selectively cancel RPC calls
      SUNRPC: Add API to force the client to disconnect
      NFSv4/flexfiles: Cancel I/O if the layout is recalled or revoked

Wolfram Sang (2):
      SUNRPC: move from strlcpy with unused retval to strscpy
      NFS: move from strlcpy with unused retval to strscpy

Ziyang Xuan (1):
      SUNRPC: use max_t() to simplify open code

yuzhe (1):
      nfs: remove unnecessary (void*) conversions.

 fs/nfs/file.c                              |   6 +-
 fs/nfs/flexfilelayout/flexfilelayout.c     | 109 ++++++++++++++++++++++++++---
 fs/nfs/inode.c                             |   6 +-
 fs/nfs/internal.h                          |   2 -
 fs/nfs/nfs42proc.c                         |   4 ++
 fs/nfs/nfs42xattr.c                        |   2 +-
 fs/nfs/nfs42xdr.c                          |   8 +++
 fs/nfs/nfs4_fs.h                           |   1 -
 fs/nfs/nfs4client.c                        |   2 +-
 fs/nfs/nfs4idmap.c                         |   2 +-
 fs/nfs/nfs4proc.c                          |   4 +-
 fs/nfs/nfs4state.c                         |  10 ++-
 fs/nfs/nfs4trace.h                         |  50 ++++++++++++-
 fs/nfs/nfsroot.c                           |   2 +-
 fs/nfs/pnfs.c                              |   9 ++-
 fs/nfs/pnfs.h                              |   9 +++
 fs/nfs/pnfs_nfs.c                          |   4 +-
 include/linux/sunrpc/clnt.h                |   1 +
 include/linux/sunrpc/sched.h               |   6 ++
 net/sunrpc/clnt.c                          |  61 ++++++++++++++--
 net/sunrpc/sched.c                         |  51 ++++++++++----
 net/sunrpc/xprt.c                          |   9 +--
 net/sunrpc/xprtmultipath.c                 |   4 +-
 net/sunrpc/xprtrdma/backchannel.c          |   2 +-
 net/sunrpc/xprtrdma/frwr_ops.c             |  20 +++---
 net/sunrpc/xprtrdma/svc_rdma_backchannel.c |   4 +-
 net/sunrpc/xprtrdma/transport.c            |   3 +-
 net/sunrpc/xprtrdma/verbs.c                |  52 +++++++-------
 net/sunrpc/xprtrdma/xprt_rdma.h            |  10 ++-
 net/sunrpc/xprtsock.c                      |   5 +-
 30 files changed, 342 insertions(+), 116 deletions(-)

             reply	other threads:[~2022-10-12 20:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 20:40 Anna Schumaker [this message]
2022-10-13 18:00 ` [GIT PULL] Please Pull NFS Client Updates for Linux 6.1 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=20221012204031.657633-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox