From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: YueHaibing <yuehaibing@huawei.com>,
Olga Kornievskaia <kolga@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfsd: Fix build error
Date: Wed, 4 Mar 2020 15:06:09 -0500 [thread overview]
Message-ID: <20200304200609.GA26924@fieldses.org> (raw)
In-Reply-To: <BC0E3531-B282-4C04-9540-C39C6F4A1A5D@oracle.com>
On Wed, Mar 04, 2020 at 01:00:12PM -0500, Chuck Lever wrote:
> Hi-
>
> > On Mar 4, 2020, at 8:18 AM, YueHaibing <yuehaibing@huawei.com> wrote:
> >
> > fs/nfsd/nfs4proc.o: In function `nfsd4_do_copy':
> > nfs4proc.c:(.text+0x23b7): undefined reference to `nfs42_ssc_close'
> > fs/nfsd/nfs4proc.o: In function `nfsd4_copy':
> > nfs4proc.c:(.text+0x5d2a): undefined reference to `nfs_sb_deactive'
> > fs/nfsd/nfs4proc.o: In function `nfsd4_do_async_copy':
> > nfs4proc.c:(.text+0x61d5): undefined reference to `nfs42_ssc_open'
> > nfs4proc.c:(.text+0x6389): undefined reference to `nfs_sb_deactive'
> >
> > Add dependency to NFSD_V4_2_INTER_SSC to fix this.
> >
> > Fixes: ce0887ac96d3 ("NFSD add nfs4 inter ssc to nfsd4_copy")
> > Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> > ---
> > fs/nfsd/Kconfig | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/fs/nfsd/Kconfig b/fs/nfsd/Kconfig
> > index f368f32..fc587a5 100644
> > --- a/fs/nfsd/Kconfig
> > +++ b/fs/nfsd/Kconfig
> > @@ -136,6 +136,7 @@ config NFSD_FLEXFILELAYOUT
> >
> > config NFSD_V4_2_INTER_SSC
> > bool "NFSv4.2 inter server to server COPY"
> > + depends on !(NFSD=y && NFS_FS=m)
>
> The new dependency is not especially clear to me; more explanation
> in the patch description about the cause of the build failure
> would definitely be helpful.
>
> NFSD_V4 can't be set unless NFSD is also set.
>
> NFS_V4_2 can't be set unless NFS_V4_1 is also set, and that cannot
> be set unless NFS_FS is also set.
>
> So what's really going on here?
I don't understand that "depends" either.
The fundamental problem, though, is that nfsd is calling nfs code
directly.
Which I noticed in earlier review and then forgot to follow up on,
sorry.
So either we:
- let nfsd depend on nfs, fix up Kconfig to reflect the fact, or
- write some code so nfsd can load nfs and find those symbols at
runtime if it needs to do a copy.
The latter's certainly doable, but it'd be simplest to do the former.
Are there actually a lot of people who want nfsd but not nfs? Does that
cause a real problem for anyone?
--b.
next prev parent reply other threads:[~2020-03-04 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 13:18 [PATCH] nfsd: Fix build error YueHaibing
2020-03-04 18:00 ` Chuck Lever
2020-03-04 20:06 ` Bruce Fields [this message]
2020-03-04 21:05 ` Chuck Lever
2020-03-04 21:20 ` Kornievskaia, Olga
2020-03-05 3:46 ` Yuehaibing
2020-03-05 15:15 ` Chuck Lever
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=20200304200609.GA26924@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=yuehaibing@huawei.com \
/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