From: Mike Snitzer <snitzer@kernel.org>
To: Janpieter Sollie via Bugspray Bot <bugbot@kernel.org>
Cc: trondmy@kernel.org, anna@kernel.org, linux-nfs@vger.kernel.org,
cel@kernel.org, jlayton@kernel.org
Subject: Re: link error while compiling localio.c
Date: Tue, 22 Oct 2024 09:57:31 -0400 [thread overview]
Message-ID: <ZxevSxHOBA7s5mUC@kernel.org> (raw)
In-Reply-To: <20241010-b219370c0-bd6df2a482ac@bugzilla.kernel.org>
On Thu, Oct 10, 2024 at 07:35:10AM +0000, Janpieter Sollie via Bugspray Bot wrote:
> Janpieter Sollie added an attachment on Kernel.org Bugzilla:
>
> Created attachment 306999
> kernel .config
>
> tried both GCC and clang:
> Clang output:
> > ld.lld: error: undefined symbol: nfs_to
> > >>> referenced by localio.c:37 (fs/nfsd/localio.c:37)
> > >>> vmlinux.o:(init_nfsd)
> > >>> referenced by localio.c:37 (/usr/src/linux/fs/nfsd/localio.c:37)
> > >>> vmlinux.o:(nfsd_localio_ops_init)
> >
> > ld.lld: error: undefined symbol: nfs_uuid_invalidate_clients
> > >>> referenced by nfsctl.c:2286 (/usr/src/linux/fs/nfsd/nfsctl.c:2286)
> > >>> vmlinux.o:(nfsd_net_pre_exit)
> >
> > ld.lld: error: undefined symbol: nfs_uuid_is_local
> > >>> referenced by localio.c:116 (/usr/src/linux/fs/nfsd/localio.c:116)
> > >>> vmlinux.o:(localio_proc_uuid_is_local)
> GCC output:
> ld: fs/nfsd/nfsctl.o: in function `nfsd_net_pre_exit':
> nfsctl.c:(.text+0x122): undefined reference to `nfs_uuid_invalidate_clients'
> ld: fs/nfsd/localio.o: in function `localio_proc_uuid_is_local':
> /usr/src/linux/fs/nfsd/localio.c:116:(.text+0x56): undefined reference to `nfs_uuid_is_local'
> ld: fs/nfsd/localio.o: in function `nfsd_localio_ops_init':
> /usr/src/linux/fs/nfsd/localio.c:37:(.text+0x2c9): undefined reference to `nfs_to'
>
> Command:
> make -j64 or make LLVM=1 -j64
>
> the config file for GCC will be attached, let me know if the clang version is desired as well
>
> As you might guess, not trimming the unused symbols fixes the issue ...
>
> File: config.txt (text/plain)
> Size: 130.19 KiB
> Link: https://bugzilla.kernel.org/attachment.cgi?id=306999
> ---
> kernel .config
>
> You can reply to this message to join the discussion.
> --
> Deet-doot-dot, I am a bot.
> Kernel.org Bugzilla (bugspray 0.1-dev)
I will report as much via bugzilla.kernel.org but for the benefit of those cc'd:
This was fixed via v6.12-rc3 commit 009b15b57485 ("nfs_common: fix
Kconfig for NFS_COMMON_LOCALIO_SUPPORT")
In the provided kernel config:
CONFIG_NFS_FS=m
CONFIG_NFSD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_NFS_COMMON_LOCALIO_SUPPORT=m
CONFIG_NFS_LOCALIO=y
My Kconfig fix will result in CONFIG_NFS_LOCALIO=m so that the symbols
are available to the nfs.ko kernel module.
But if you have any further issues, certainly let me know.
Thanks,
Mike
next prev parent reply other threads:[~2024-10-22 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 7:35 link error while compiling localio.c Janpieter Sollie via Bugspray Bot
2024-10-10 7:35 ` Janpieter Sollie via Bugspray Bot
2024-10-10 8:05 ` Janpieter Sollie via Bugspray Bot
2024-10-10 10:55 ` The Linux kernel's regression tracker (Thorsten Leemhuis) via Bugspray Bot
2024-10-22 10:40 ` The Linux kernel's regression tracker (Thorsten Leemhuis) via Bugspray Bot
2024-10-22 13:57 ` Mike Snitzer [this message]
2024-10-22 14:00 ` Mike Snitzer via Bugspray Bot
2024-10-22 14:15 ` Mike Snitzer via Bugspray Bot
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=ZxevSxHOBA7s5mUC@kernel.org \
--to=snitzer@kernel.org \
--cc=anna@kernel.org \
--cc=bugbot@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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