From: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 0/3] NFS/RDMA server changes for v4.16
Date: Wed, 03 Jan 2018 15:42:10 -0500 [thread overview]
Message-ID: <20180103203849.7074.9609.stgit@klimt.1015granger.net> (raw)
Hi Bruce-
Would you consider these patches for merging into v4.16?
Changes since v1:
- Rebased on v4.15-rc6
- Address a 0day robot complaint in nfsd3_proc_symlink
- Properly handle error return from svc_rdma_handle_bc_reply
---
Chuck Lever (3):
svcrdma: Post Receives in the Receive completion handler
NFSD: Clean up write argument XDR decoders
NFSD: Clean up symlink argument XDR decoders
fs/nfsd/nfs3proc.c | 18 ++++-
fs/nfsd/nfs3xdr.c | 67 ++++-------------
fs/nfsd/nfs4proc.c | 37 +++-------
fs/nfsd/nfs4xdr.c | 11 ++-
fs/nfsd/nfsproc.c | 23 ++++--
fs/nfsd/nfsxdr.c | 63 ++++++++--------
fs/nfsd/xdr.h | 3 +
fs/nfsd/xdr3.h | 3 +
fs/nfsd/xdr4.h | 3 +
include/linux/sunrpc/svc.h | 4 +
include/linux/sunrpc/svc_rdma.h | 2 -
net/sunrpc/svc.c | 109 ++++++++++++++++++++++++++++
net/sunrpc/xprtrdma/svc_rdma_backchannel.c | 5 -
net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 9 --
net/sunrpc/xprtrdma/svc_rdma_sendto.c | 6 --
net/sunrpc/xprtrdma/svc_rdma_transport.c | 25 ++----
16 files changed, 225 insertions(+), 163 deletions(-)
--
Chuck Lever
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-01-03 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 20:42 Chuck Lever [this message]
[not found] ` <20180103203849.7074.9609.stgit-Hs+gFlyCn65vLzlybtyyYzGyq/o6K9yX@public.gmane.org>
2018-01-03 20:42 ` [PATCH v2 1/3] svcrdma: Post Receives in the Receive completion handler Chuck Lever
2018-01-03 20:42 ` [PATCH v2 2/3] NFSD: Clean up write argument XDR decoders Chuck Lever
2018-01-03 20:42 ` [PATCH v2 3/3] NFSD: Clean up symlink " Chuck Lever
[not found] ` <20180103204235.7074.64787.stgit-Hs+gFlyCn65vLzlybtyyYzGyq/o6K9yX@public.gmane.org>
2018-01-22 22:00 ` J. Bruce Fields
[not found] ` <20180122220004.GB16585-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2018-01-23 1:09 ` Chuck Lever
[not found] ` <E0C9EADF-504F-4CCF-933E-07CD6AE041DE-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2018-01-23 20:52 ` Bruce Fields
[not found] ` <20180123205200.GB4484-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2018-01-23 22:30 ` Chuck Lever
[not found] ` <5D0F8C69-3F7B-4E42-91F3-3A280C440F81-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2018-01-25 16:33 ` Bruce Fields
[not found] ` <20180125163356.GB20350-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2018-01-25 16:40 ` Chuck Lever
2018-01-16 21:31 ` [PATCH v2 0/3] NFS/RDMA server changes for v4.16 Chuck Lever
[not found] ` <BD4AB89D-D4A5-4576-A9EE-4D0A485F13E1-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2018-01-16 21:33 ` Bruce Fields
[not found] ` <20180116213343.GD21173-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2018-01-17 14:44 ` 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=20180103203849.7074.9609.stgit@klimt.1015granger.net \
--to=chuck.lever-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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