From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:openEuler-1.0-LTS 1743/1743] arch/x86/mm/cpu_entry_area.c:155:5: warning: no previous prototype for 'arch_get_kallsym'
Date: Mon, 4 Aug 2025 08:30:48 +0200 [thread overview]
Message-ID: <202508040829.QB64jfaH-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: ba07135cf74b1424e2f7f0c60e59c5b206ab320c
commit: d83212d5dd6761625fe87cc23016bbaa47303271 [1743/1743] kallsyms, x86: Export addresses of PTI entry trampolines
config: x86_64-buildonly-randconfig-2004-20250802 (https://download.01.org/0day-ci/archive/20250804/202508040829.QB64jfaH-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250804/202508040829.QB64jfaH-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/202508040829.QB64jfaH-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/mm/cpu_entry_area.c:155:5: warning: no previous prototype for 'arch_get_kallsym' [-Wmissing-prototypes]
155 | int arch_get_kallsym(unsigned int symnum, unsigned long *value, char *type,
| ^~~~~~~~~~~~~~~~
vim +/arch_get_kallsym +155 arch/x86/mm/cpu_entry_area.c
153
154 #ifdef CONFIG_X86_64
> 155 int arch_get_kallsym(unsigned int symnum, unsigned long *value, char *type,
156 char *name)
157 {
158 unsigned int cpu, ncpu = 0;
159
160 if (symnum >= num_possible_cpus())
161 return -EINVAL;
162
163 for_each_possible_cpu(cpu) {
164 if (ncpu++ >= symnum)
165 break;
166 }
167
168 *value = (unsigned long)&get_cpu_entry_area(cpu)->entry_trampoline;
169 *type = 't';
170 strlcpy(name, "__entry_SYSCALL_64_trampoline", KSYM_NAME_LEN);
171
172 return 0;
173 }
174 #endif
175
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-04 6:31 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=202508040829.QB64jfaH-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.