From: Jeff Layton <jlayton@kernel.org>
To: Dai Ngo <dai.ngo@oracle.com>, chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: PATCH [0/2] NFSD: use CB_GETATTR to handle GETATTR conflict with write delegation
Date: Tue, 13 Feb 2024 15:24:28 -0500 [thread overview]
Message-ID: <b7250dbd8b69eabb03bef36ad6ba908999ed8054.camel@kernel.org> (raw)
In-Reply-To: <1707846447-21042-1-git-send-email-dai.ngo@oracle.com>
On Tue, 2024-02-13 at 09:47 -0800, Dai Ngo wrote:
> Currently GETATTR conflict with a write delegation is handled by
> recalling the delegation before replying to the GETATTR.
>
> This patch series add supports for CB_GETATTR callback to get the latest
> change_info and size information of the file from the client that holds
> the delegation to reply to the GETATTR from the second client.
>
> NOTE: this patch series is mostly the same as the previous patches which
> were backed out when un unrelated problem of NFSD server hang on reboot
> was reported.
>
> The only difference is the wait_on_bit() in nfsd4_deleg_getattr_conflict was
> replaced with wait_on_bit_timeout() with 30ms timeout to avoid a potential
> DOS attack by exhausting NFSD kernel threads with GETATTR conflicts.
>
> fs/nfsd/nfs4callback.c | 97 +++++++++++++++++++++++++++++++++++-
> fs/nfsd/nfs4state.c | 119 ++++++++++++++++++++++++++++++++++++++++----
> fs/nfsd/nfs4xdr.c | 10 +++-
> fs/nfsd/nfsd.h | 1 +
> fs/nfsd/state.h | 24 ++++++++-
> fs/nfsd/xdr4cb.h | 18 +++++++
> 6 files changed, 255 insertions(+), 14 deletions(-)
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-02-13 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 17:47 PATCH [0/2] NFSD: use CB_GETATTR to handle GETATTR conflict with write delegation Dai Ngo
2024-02-13 17:47 ` [PATCH 1/2] NFSD: add supports for CB_GETATTR callback Dai Ngo
2024-02-13 17:47 ` [PATCH 2/2] NFSD: handle GETATTR conflict with write delegation Dai Ngo
2024-02-14 14:50 ` Chuck Lever
2024-02-14 18:10 ` dai.ngo
2024-02-14 18:14 ` Chuck Lever
2024-02-14 18:22 ` dai.ngo
2024-02-15 13:55 ` Chuck Lever
2024-02-13 20:24 ` Jeff Layton [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=b7250dbd8b69eabb03bef36ad6ba908999ed8054.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).