linux-kernel - [GIT PULL] nfsd bugfixes for 4.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20150511214228.GC23754@fieldses.org>
Date:	Mon, 11 May 2015 17:42:28 -0400
From:	bfields@...ldses.org (J. Bruce Fields)
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [GIT PULL] nfsd bugfixes for 4.1

Please pull nfsd fixes for 4.1 from

  git://linux-nfs.org/~bfields/linux.git for-4.1

Mainly pnfs fixes (and for problems with generic callback code made more
obvious by pnfs).

--b.

----------------------------------------------------------------
Christoph Hellwig (5):
      nfsd/blocklayout: pretend we can send deviceid notifications
      nfsd: fix the check for confirmed openowner in nfs4_preprocess_stateid_op
      nfsd: split transport vs operation errors for callbacks
      nfsd: fix callback restarts
      nfsd: skip CB_NULL probes for 4.1 or later

Sachin Bhamare (1):
      nfsd: fix pNFS return on close semantics

Scott Mayhew (1):
      svcrpc: fix potential GSSX_ACCEPT_SEC_CONTEXT decoding failures

 fs/nfsd/blocklayout.c             |  11 +++
 fs/nfsd/nfs4callback.c            | 119 ++++++++++++++----------------
 fs/nfsd/nfs4state.c               | 147 +++++++++++++++++++++++++++++++++-----
 fs/nfsd/state.h                   |  19 ++++-
 fs/nfsd/xdr4.h                    |   1 +
 net/sunrpc/auth_gss/gss_rpc_xdr.c |  23 ++++--
 6 files changed, 228 insertions(+), 92 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/