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 v2 0/2] NFSD: use CB_GETATTR to handle GETATTR conflict with write delegation
Date: Mon, 18 Sep 2023 11:42:08 -0400 [thread overview]
Message-ID: <f2d0018145fda00a25835a7ba7347515d8e06015.camel@kernel.org> (raw)
In-Reply-To: <1694648301-26746-1-git-send-email-dai.ngo@oracle.com>
On Wed, 2023-09-13 at 16:38 -0700, 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.
>
> v2:
> . fix kernel test robot report of missing function parameter description
> of nfsd4_deleg_getattr_conflict()
>
This all looks good to me. Nice work, Dai!
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2023-09-18 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 23:38 [PATCH v2 0/2] NFSD: use CB_GETATTR to handle GETATTR conflict with write delegation Dai Ngo
2023-09-13 23:38 ` [PATCH v2 1/2] NFSD: add supports for CB_GETATTR callback Dai Ngo
2023-09-13 23:38 ` [PATCH v2 2/2] NFSD: handle GETATTR conflict with write delegation Dai Ngo
2023-09-15 15:57 ` [PATCH v2 0/2] NFSD: use CB_GETATTR to " Chuck Lever
2023-09-18 15:42 ` 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=f2d0018145fda00a25835a7ba7347515d8e06015.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