From: "J. Bruce Fields" <bfields@fieldses.org>
To: Benny Halevy <bhalevy@panasas.com>
Cc: pnfs@linux-nfs.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 28/44] nfsd41: use the maximum operations per compound in nfsd4_compoundargs
Date: Thu, 18 Jun 2009 18:14:43 -0400 [thread overview]
Message-ID: <20090618221443.GH12234@fieldses.org> (raw)
In-Reply-To: <1245115233-7725-1-git-send-email-bhalevy@panasas.com>
On Tue, Jun 16, 2009 at 04:20:33AM +0300, Benny Halevy wrote:
> From: Andy Adamson <andros@netapp.com>
>
> The size of the nfsd4_op array in nfsd4_compoundargs determines the
> supported maximum number of operations.
This is another one that is a clear straightfoward bugfix to existing
code, so please put it right up at the front of the patch series.
(ALso a comment that more clearly explains the problem would help, say,
like:
"We're returning NFSD_MAX_OPS_PER_COMPOUND = 16 to 4.1 clients,
but the limit the server actually enforces (in
nfsd4_decode_compound) is 8. Fix the value of
NFSD_MAX_OPS_PER_COMPOUND to return the correct value to 4.1
clients."
)
--b.
>
> Signed-off-by: Andy Adamson <andros@netapp.com>
> Signed-off-by: Benny Halevy <bhalevy@panasas.com>
> ---
> include/linux/nfsd/state.h | 3 +--
> include/linux/nfsd/xdr4.h | 2 +-
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/nfsd/state.h b/include/linux/nfsd/state.h
> index aea8137..093f165 100644
> --- a/include/linux/nfsd/state.h
> +++ b/include/linux/nfsd/state.h
> @@ -94,8 +94,7 @@ struct nfs4_cb_conn {
>
> #define NFSD_MAX_SLOTS_PER_SESSION 16
> #define NFSD_SLOT_CACHE_SIZE 512
> -/* Maximum number of operations per session compound */
> -#define NFSD_MAX_OPS_PER_COMPOUND 16
> +#define NFSD_MAX_OPS_PER_COMPOUND 8
>
> struct nfsd4_slot {
> bool sl_inuse;
> diff --git a/include/linux/nfsd/xdr4.h b/include/linux/nfsd/xdr4.h
> index 84ac4bb..d99c8fe 100644
> --- a/include/linux/nfsd/xdr4.h
> +++ b/include/linux/nfsd/xdr4.h
> @@ -446,7 +446,7 @@ struct nfsd4_compoundargs {
> u32 minorversion;
> u32 opcnt;
> struct nfsd4_op *ops;
> - struct nfsd4_op iops[8];
> + struct nfsd4_op iops[NFSD_MAX_OPS_PER_COMPOUND];
> };
>
> struct nfsd4_compoundres {
> --
> 1.6.3
>
next prev parent reply other threads:[~2009-06-18 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 1:20 [PATCH 28/44] nfsd41: use the maximum operations per compound in nfsd4_compoundargs Benny Halevy
2009-06-18 22:14 ` J. Bruce Fields [this message]
2009-06-18 22:17 ` J. Bruce Fields
2009-06-19 0:49 ` Mike Mackovitch
[not found] ` <20090619004936.GB19581-kyl61TxYs+X2fBVCVOL8/A@public.gmane.org>
2009-06-19 1:04 ` J. Bruce Fields
2009-06-19 2:27 ` Mike Mackovitch
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=20090618221443.GH12234@fieldses.org \
--to=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.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