From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v1 0/2] NFSD: Clean ups for recent XDR work
Date: Sat, 2 Oct 2021 16:38:46 -0400 [thread overview]
Message-ID: <20211002203846.GD26608@fieldses.org> (raw)
In-Reply-To: <163303585936.5125.6042907247616993649.stgit@klimt.1015granger.net>
On Thu, Sep 30, 2021 at 05:06:09PM -0400, Chuck Lever wrote:
> As we discussed, here are a couple of minor improvements for the
> xdr_stream_subsegment() API added when the NFSv4 XDR functions were
> recently overhauled. Notably, the second patch changes the NFSv2 and
> NFSv3 decoders to work like the NFSv4 one.
Looks good to me; applying.
--b.
>
> ---
>
> Chuck Lever (2):
> SUNRPC: xdr_stream_subsegment() must handle non-zero page_bases
> NFSD: Have legacy NFSD WRITE decoders use xdr_stream_subsegment()
>
>
> fs/nfsd/nfs3proc.c | 3 +--
> fs/nfsd/nfs3xdr.c | 12 ++----------
> fs/nfsd/nfs4proc.c | 3 +--
> fs/nfsd/nfsproc.c | 3 +--
> fs/nfsd/nfsxdr.c | 9 +--------
> fs/nfsd/xdr.h | 2 +-
> fs/nfsd/xdr3.h | 2 +-
> include/linux/sunrpc/svc.h | 3 +--
> net/sunrpc/svc.c | 11 ++++++-----
> net/sunrpc/xdr.c | 32 +++++++++++++++++---------------
> 10 files changed, 32 insertions(+), 48 deletions(-)
>
> --
> Chuck Lever
prev parent reply other threads:[~2021-10-02 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 21:06 [PATCH v1 0/2] NFSD: Clean ups for recent XDR work Chuck Lever
2021-09-30 21:06 ` [PATCH v1 1/2] SUNRPC: xdr_stream_subsegment() must handle non-zero page_bases Chuck Lever
2021-09-30 21:06 ` [PATCH v1 2/2] NFSD: Have legacy NFSD WRITE decoders use xdr_stream_subsegment() Chuck Lever
2021-10-02 20:38 ` J. Bruce Fields [this message]
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=20211002203846.GD26608@fieldses.org \
--to=bfields@fieldses.org \
--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.