From: kernel test robot <lkp@intel.com>
To: Viktor Malik <vmalik@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: [linux-next:master 3796/4036] kernel/module/internal.h:260:56: error: expected ';', ',' or ')' before 'const'
Date: Thu, 16 Mar 2023 13:18:01 +0800 [thread overview]
Message-ID: <202303161311.Qv4gDU9T-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6f72958a49f68553f2b6ff713e8c8e51a34c1e1e
commit: 2a6427ca8f3a8f08498c7b60e486c95af88d0afd [3796/4036] bpf: Fix attaching fentry/fexit/fmod_ret/lsm to modules
config: m68k-randconfig-r001-20230313 (https://download.01.org/0day-ci/archive/20230316/202303161311.Qv4gDU9T-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2a6427ca8f3a8f08498c7b60e486c95af88d0afd
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 2a6427ca8f3a8f08498c7b60e486c95af88d0afd
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=m68k olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=m68k SHELL=/bin/bash kernel/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303161311.Qv4gDU9T-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/module/main.c:59:
>> kernel/module/internal.h:260:56: error: expected ';', ',' or ')' before 'const'
260 | const char *name)
| ^~~~~
--
In file included from kernel/bpf/verifier.c:27:
>> kernel/bpf/../module/internal.h:260:56: error: expected ';', ',' or ')' before 'const'
260 | const char *name)
| ^~~~~
kernel/bpf/verifier.c: In function 'bpf_check_attach_target':
>> kernel/bpf/verifier.c:18488:48: error: implicit declaration of function 'find_kallsyms_symbol_value'; did you mean 'kallsyms_symbol_value'? [-Werror=implicit-function-declaration]
18488 | addr = find_kallsyms_symbol_value(mod, tname);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| kallsyms_symbol_value
cc1: some warnings being treated as errors
vim +260 kernel/module/internal.h
250
251 static inline bool sect_empty(const Elf_Shdr *sect)
252 {
253 return !(sect->sh_flags & SHF_ALLOC) || sect->sh_size == 0;
254 }
255 #else /* !CONFIG_KALLSYMS */
256 static inline void init_build_id(struct module *mod, const struct load_info *info) { }
257 static inline void layout_symtab(struct module *mod, struct load_info *info) { }
258 static inline void add_kallsyms(struct module *mod, const struct load_info *info) { }
259 static inline unsigned long find_kallsyms_symbol_value(struct module *mod
> 260 const char *name)
261 {
262 return 0;
263 }
264 #endif /* CONFIG_KALLSYMS */
265
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-16 5:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202303161311.Qv4gDU9T-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vmalik@redhat.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