From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dai Ngo <dai.ngo@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/1] NFSv4.2: Fix NFS4ERR_STALE with inter server copy
Date: Thu, 8 Oct 2020 13:58:03 -0400 [thread overview]
Message-ID: <20201008175803.GA18179@fieldses.org> (raw)
In-Reply-To: <20201008012513.89989-1-dai.ngo@oracle.com>
On Wed, Oct 07, 2020 at 09:25:12PM -0400, Dai Ngo wrote:
> This cover email is intended for including my test results.
>
> This patch adds the ops table in nfs_common for knfsd to access
> NFS client modules without calling these functions directly.
>
> The client module registers their functions and deregisters them
> when the module is loaded and unloaded respectively.
>
> fs/nfs/nfs4file.c | 44 ++++++++++++--
> fs/nfs/nfs4super.c | 6 ++
> fs/nfs/super.c | 20 +++++++
> fs/nfs_common/Makefile | 1 +
> fs/nfs_common/nfs_ssc.c | 136 +++++++++++++++++++++++++++++++++++++++++++
> fs/nfsd/Kconfig | 2 +-
> fs/nfsd/nfs4proc.c | 3 +-
> include/linux/nfs_ssc.h | 77 ++++++++++++++++++++++++
> 8 files changed, 281 insertions(+), 8 deletions(-)
>
> Test Results:
>
> Upstream version used for testing: 5.9-rc5
>
> |----------------------------------------------------------|
> | NFSD | NFS_FS | NFS_V4 | RESULTS |
> |----------------------------------------------------------|
> | m | y | m | inter server copy OK |
> |----------------------------------------------------------|
> | m | m | m | inter server copy OK |
> |----------------------------------------------------------|
> | m | m | y (m) | inter server copy OK |
> |----------------------------------------------------------|
> | m | y | y | inter server copy OK |
> |----------------------------------------------------------|
> | m | n | n | NFS4ERR_STALE error |
> |----------------------------------------------------------|
Why are there two? And how are you getting that NFS4ERR_STALE case?
NFSD_V4_2_INTER_SSC depends on NFS_FS, so it shouldn't be possible to
build server-to-server-copy support without building the client. And if
you don't build NFSD_V4_2_INTER_SSC at all, then I think it should be
returning NOTSUPP instead of STALE.
--b.
> |----------------------------------------------------------|
> | NFSD | NFS_FS | NFS_V4 | RESULTS |
> |----------------------------------------------------------|
> | y | y | m | inter server copy OK |
> |----------------------------------------------------------|
> | y | m | m | inter server copy OK |
> |----------------------------------------------------------|
> | y | m | y (m) | inter server copy OK |
> |----------------------------------------------------------|
> | y | y | y | inter server copy OK |
> |----------------------------------------------------------|
> | y | n | n | NFS4ERR_STALE error |
> |----------------------------------------------------------|
>
> NOTE:
> When NFS_V4=y and NFS_FS=m, the build process automatically builds
> with NFS_V4=m and ignores the setting NFS_V4=y in the config file.
>
> This probably due to NFS_V4 in fs/nfs/Kconfig is configured to
> depend on NFS_FS.
next prev parent reply other threads:[~2020-10-08 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 1:25 [PATCH v2 0/1] NFSv4.2: Fix NFS4ERR_STALE with inter server copy Dai Ngo
2020-10-08 1:25 ` [PATCH v2 1/1] NFSv4.2: Fix NFS4ERR_STALE error when doing " Dai Ngo
2020-10-08 2:56 ` kernel test robot
2020-10-08 3:11 ` kernel test robot
2020-10-08 3:11 ` [RFC PATCH] NFSv4.2: nfs_ssc_clnt_ops_tbl can be static kernel test robot
2020-10-08 3:24 ` [PATCH v2 1/1] NFSv4.2: Fix NFS4ERR_STALE error when doing inter server copy kernel test robot
2020-10-08 17:58 ` J. Bruce Fields [this message]
2020-10-08 18:29 ` [PATCH v2 0/1] NFSv4.2: Fix NFS4ERR_STALE with " Dai Ngo
2020-10-08 19:47 ` J. Bruce Fields
2020-10-08 21:15 ` Dai Ngo
2020-10-08 21:17 ` Dai Ngo
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=20201008175803.GA18179@fieldses.org \
--to=bfields@fieldses.org \
--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).