From: Trond Myklebust <trondmy@gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] bugfixes for RPCSEC_GSS client support
Date: Wed, 2 Jan 2019 17:53:09 -0500 [thread overview]
Message-ID: <20190102225313.2097-1-trond.myklebust@hammerspace.com> (raw)
These patches address a couple of issues that are mainly affecting our
RPCSEC_GSS client support.
Trond Myklebust (4):
SUNRPC: Ensure rq_bytes_sent is reset before request transmission
SUNRPC: Fix the RPCSEC_GSS sequence semantics after request
re-encoding
SUNRPC: Allow for some re-ordering of RPCSEC_GSS requests on the
server
SUNRPC: Ensure we respect the RPCSEC_GSS sequence number limit
net/sunrpc/auth_gss/auth_gss.c | 22 +++++++++++++++-------
net/sunrpc/clnt.c | 20 ++++++++++++--------
net/sunrpc/xprt.c | 7 +++++++
3 files changed, 34 insertions(+), 15 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-02 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 22:53 Trond Myklebust [this message]
2019-01-02 22:53 ` [PATCH 1/4] SUNRPC: Ensure rq_bytes_sent is reset before request transmission Trond Myklebust
2019-01-02 22:53 ` [PATCH 2/4] SUNRPC: Fix the RPCSEC_GSS sequence semantics after request re-encoding Trond Myklebust
2019-01-02 22:53 ` [PATCH 3/4] SUNRPC: Allow for some re-ordering of RPCSEC_GSS requests on the server Trond Myklebust
2019-01-02 22:53 ` [PATCH 4/4] SUNRPC: Ensure we respect the RPCSEC_GSS sequence number limit Trond Myklebust
2019-01-03 15:29 ` [PATCH 1/4] SUNRPC: Ensure rq_bytes_sent is reset before request transmission Chuck Lever
2019-01-03 16:05 ` Trond Myklebust
2019-01-03 16:17 ` Tom Talpey
2019-01-03 16:27 ` Trond Myklebust
2019-01-03 16:39 ` Chuck Lever
2019-01-03 16:41 ` Chuck Lever
2019-01-03 18:09 ` Trond Myklebust
2019-01-03 17:15 ` [PATCH 0/4] bugfixes for RPCSEC_GSS client support Chuck Lever
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=20190102225313.2097-1-trond.myklebust@hammerspace.com \
--to=trondmy@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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.