linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull NFS client updates
Date: Tue, 13 Dec 2022 10:35:50 -0500	[thread overview]
Message-ID: <a91ef5f6937333955610acebf92c8efb2f9b8391.camel@kernel.org> (raw)

Hi Linus,

The following changes since commit b7b275e60bcd5f89771e865a8239325f86d9927d:

  Linux 6.1-rc7 (2022-11-27 13:31:48 -0800)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.2-1

for you to fetch changes up to 7fd461c47c6cfab4ca4d003790ec276209e52978:

  NFSv4.2: Change the default KConfig value for READ_PLUS (2022-12-10 13:24:59 -0500)

Cheers,
  Trond

----------------------------------------------------------------
NFS client updates for Linux 6.2

Highlights include:

Bugfixes
- Fix a NULL pointer dereference in the mount parser
- Fix a memory stomp in decode_attr_security_label
- Fix a credential leak in _nfs4_discover_trunking()
- Fix a buffer leak in rpcrdma_req_create()
- Fix a leaked socket in rpc_sockname()
- Fix a deadlock between nfs4_open_recover_helper() and delegreturn
- Fix an Oops in nfs_d_automount()
- Fix a potential race in nfs_call_unlink()
- Multiple fixes for the open context mode
- NFSv4.2 READ_PLUS fixes
- Fix a regression in which small rsize/wsize values are being forbidden
- Fail client initialisation if the NFSv4.x state manager thread can't run
- avoid spurious warning of lost lock that is being unlocked.
- Ensure the initialisation of struct nfs4_label

Features and cleanups
- Trigger the "ls -l" readdir heuristic sooner
- Clear the file access cache upon login to ensure supplementary group
  info is in sync between the client and server
- pnfs: Fix up the logging of layout stateids
- NFSv4.2: Change the default KConfig value for READ_PLUS
- Use sysfs_emit() instead of scnprintf() where appropriate

----------------------------------------------------------------
Anna Schumaker (4):
      NFSv4.2: Set the correct size scratch buffer for decoding READ_PLUS
      NFSv4.2: Fix up READ_PLUS alignment
      NFS: Allow very small rsize & wsize again
      NFSv4.2: Change the default KConfig value for READ_PLUS

Benjamin Coddington (1):
      NFS: Trigger the "ls -l" readdir heuristic sooner

ChenXiaoSong (2):
      NFS: make sure open context mode have FMODE_EXEC when file open for exec
      NFSv4: check FMODE_EXEC from open context mode in nfs4_opendata_access()

Hawkins Jiawei (1):
      nfs: fix possible null-ptr-deref when parsing param

NeilBrown (1):
      NFS: avoid spurious warning of lost lock that is being unlocked.

Trond Myklebust (11):
      NFS: Clear the file access cache upon login
      NFSv4.2: Clear FATTR4_WORD2_SECURITY_LABEL when done decoding
      NFSv4.2: Always decode the security label
      NFSv4.2: Fix a memory stomp in decode_attr_security_label
      NFSv4.2: Fix initialisation of struct nfs4_label
      NFSv4: Fix a credential leak in _nfs4_discover_trunking()
      NFSv4: Fix a deadlock between nfs4_open_recover_helper() and delegreturn
      NFS: Fix an Oops in nfs_d_automount()
      NFS: Fix a race in nfs_call_unlink()
      NFS4.x/pnfs: Fix up logging of layout stateids
      NFSv4.x: Fail client initialisation if state manager thread can't run

Wang ShaoBo (1):
      SUNRPC: Fix missing release socket in rpc_sockname()

Zhang Xiaoxu (1):
      xprtrdma: Fix regbuf data not freed in rpcrdma_req_create()

ye xingchen (2):
      NFS: use sysfs_emit() to instead of scnprintf()
      fs: nfs: sysfs: use sysfs_emit() to instead of scnprintf()

 fs/nfs/Kconfig              |  8 +++----
 fs/nfs/dir.c                | 32 +++++++++++++++++++++++--
 fs/nfs/fs_context.c         |  6 +++++
 fs/nfs/inode.c              |  3 ++-
 fs/nfs/internal.h           |  6 ++---
 fs/nfs/namespace.c          |  4 ++--
 fs/nfs/nfs42xdr.c           |  9 +++----
 fs/nfs/nfs4_fs.h            |  1 +
 fs/nfs/nfs4file.c           | 12 ++++------
 fs/nfs/nfs4proc.c           | 57 +++++++++++++++++++++++++--------------------
 fs/nfs/nfs4state.c          |  5 +++-
 fs/nfs/nfs4trace.h          |  4 ++--
 fs/nfs/nfs4xdr.c            | 22 +++++++----------
 fs/nfs/sysfs.c              |  2 +-
 fs/nfs/unlink.c             |  1 +
 include/linux/nfs_fs.h      |  1 +
 net/sunrpc/clnt.c           |  2 +-
 net/sunrpc/xprtrdma/verbs.c |  2 +-
 18 files changed, 108 insertions(+), 69 deletions(-)

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



             reply	other threads:[~2022-12-13 15:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 15:35 Trond Myklebust [this message]
2022-12-13 18:13 ` [GIT PULL] Please pull NFS client updates pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2015-07-02 16:21 Trond Myklebust
2015-02-20 16:16 Trond Myklebust
2015-02-20 16:19 ` Christoph Hellwig
2015-02-20 16:22   ` Trond Myklebust
2014-06-10 21:42 Trond Myklebust
2014-03-09 16:22 Trond Myklebust
2013-07-11 18:18 Myklebust, Trond
2013-07-08 17:59 Myklebust, Trond
2012-03-22 14:59 Myklebust, Trond
2011-05-29 16:30 Trond Myklebust

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=a91ef5f6937333955610acebf92c8efb2f9b8391.camel@kernel.org \
    --to=trondmy@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 NNTP newsgroup(s).