From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>,
"Amir Goldstein" <amir73il@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Christian Brauner" <brauner@kernel.org>,
"Jan Kara" <jack@suse.cz>, "Jeff Layton" <jlayton@kernel.org>
Subject: Re: [linux-next:master 14416/15220] fs/exportfs/expfs.c:357:5: error: expected identifier or '('
Date: Thu, 26 Oct 2023 16:37:18 +0200 [thread overview]
Message-ID: <dd4bf45e-2ef3-4975-904d-f72c3d4af7c7@app.fastmail.com> (raw)
In-Reply-To: <202310262151.renqMvme-lkp@intel.com>
On Thu, Oct 26, 2023, at 15:49, kernel test robot wrote:
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> head: 2ef7141596eed0b4b45ef18b3626f428a6b0a822
> commit: dfaf653dc41557548b2e75e6cd837071f7c63289 [14416/15220]
> exportfs: make ->encode_fh() a mandatory method for NFS export
> config: hexagon-randconfig-r015-20211224
> (https://download.01.org/0day-ci/archive/20231026/202310262151.renqMvme-lkp@intel.com/config)
> compiler: clang version 16.0.4
> (https://github.com/llvm/llvm-project.git
> ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce (this is a W=1 build):
> (https://download.01.org/0day-ci/archive/20231026/202310262151.renqMvme-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new
> version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes:
> https://lore.kernel.org/oe-kbuild-all/202310262151.renqMvme-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> fs/exportfs/expfs.c:357:5: error: expected identifier or '('
> int generic_encode_ino32_fh(struct inode *inode, __u32 *fh, int
> *max_len,
> ^
> include/linux/exportfs.h:286:33: note: expanded from macro
This bit is trivially fixed by allowing the protoype to
be visible for CONFIG_EXPORTFS=m
--- a/include/linux/exportfs.h
+++ b/include/linux/exportfs.h
@@ -314,7 +314,7 @@ extern struct dentry *exportfs_decode_fh(struct vfsmount *mnt, struct fid *fid,
/*
* Generic helpers for filesystems.
*/
-#ifdef CONFIG_EXPORTFS
+#if IS_ENABLED(CONFIG_EXPORTFS)
int generic_encode_ino32_fh(struct inode *inode, __u32 *fh, int *max_len,
struct inode *parent);
#else
but then we instead get link failures when the callers are
built-in:
x86_64-linux-ld: fs/ext4/super.o:(.rodata+0x11a0): undefined reference to `generic_encode_ino32_fh'
x86_64-linux-ld: fs/ext2/super.o:(.rodata+0x3a0): undefined reference to `generic_encode_ino32_fh'
x86_64-linux-ld: fs/fat/nfs.o:(.rodata+0x120): undefined reference to `generic_encode_ino32_fh'
x86_64-linux-ld: fs/ntfs3/super.o:(.rodata+0x2a0): undefined reference to `generic_encode_ino32_fh'
x86_64-linux-ld: fs/befs/linuxvfs.o:(.rodata+0x240): undefined reference to `generic_encode_ino32_fh'
Could this function just be move to fs/libfs.c or similar?
Arnd
next prev parent reply other threads:[~2023-10-26 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 13:49 kernel test robot
2023-10-26 14:37 ` Arnd Bergmann [this message]
2023-10-26 15:15 ` Amir Goldstein
2023-10-26 20:25 ` Amir Goldstein
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=dd4bf45e-2ef3-4975-904d-f72c3d4af7c7@app.fastmail.com \
--to=arnd@arndb.de \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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