From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] NFSD: Revert setting op_encode_lockowner_maxsz
Date: Mon, 11 Aug 2014 16:01:18 -0400 [thread overview]
Message-ID: <20140811200118.GG9095@fieldses.org> (raw)
In-Reply-To: <53E2EE2E.9040007@gmail.com>
On Thu, Aug 07, 2014 at 11:10:38AM +0800, Kinglong Mee wrote:
> Commit 8c7424cff6 (nfsd4: don't try to encode conflicting owner if low on space)
> set op_encode_lockowner_maxsz to zero.
>
> If setting op_encode_lockowner_maxsz to zero, nfsd will not encode
> the owner of conflock forever.
Right, so the problem is that the lock reply encoder is unique in that
it will happily adjust the xdr encoding if it's running out of space.
This came about with 8c7424cff6 "nfsd4: don't try to encode conflicting
owner if low on space". The problem is that:
- the maximum size of a lock reply is kind of big (the original
calculation below is actually wrong, IDMAP_NAMESZ should be
NFS4_OPAQUE_LIMIT).
- we may not be the only server that's been sloppy about
enforcing the theoretical maximum here, and I'd rather be
forgiving to clients that don't insist on the theoretical
maximum maxresp_cached.
So best seems just to allow a LOCK even if space is insufficient and
just throw out the conflicting lockowner if there isn't enough space,
since large lockowners should be rare and we don't care about the
conflicting lockowner anyway.
So anyway we need to leave the maximum reserved in rq_reserved without
changing the check we make before executing the LOCK.
--b.
>
> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> ---
> fs/nfsd/nfs4proc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index 084e46e..55635a8 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -1417,8 +1417,7 @@ out:
> #define op_encode_change_info_maxsz (5)
> #define nfs4_fattr_bitmap_maxsz (4)
>
> -/* We'll fall back on returning no lockowner if run out of space: */
> -#define op_encode_lockowner_maxsz (0)
> +#define op_encode_lockowner_maxsz (1 + XDR_QUADLEN(IDMAP_NAMESZ))
> #define op_encode_lock_denied_maxsz (8 + op_encode_lockowner_maxsz)
>
> #define nfs4_owner_maxsz (1 + XDR_QUADLEN(IDMAP_NAMESZ))
> --
> 1.9.3
>
next prev parent reply other threads:[~2014-08-11 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 3:10 [PATCH 2/2] NFSD: Revert setting op_encode_lockowner_maxsz Kinglong Mee
2014-08-11 20:01 ` J. Bruce Fields [this message]
2014-08-12 17:58 ` J. Bruce Fields
2014-08-15 13:44 ` Kinglong Mee
2014-08-15 13:55 ` J. Bruce Fields
2014-08-15 14:29 ` Kinglong Mee
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=20140811200118.GG9095@fieldses.org \
--to=bfields@fieldses.org \
--cc=kinglongmee@gmail.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.