From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [luto:x86/fixes 21/26] arch/x86/entry/common.c:217:24: warning: no previous prototype for function 'ret_from_fork'
Date: Tue, 02 Mar 2021 16:16:48 +0800 [thread overview]
Message-ID: <202103021643.DYcErR4a-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2507 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/fixes
head: 5a71c0b98407b8fc659967e261ce84da00270892
commit: b529690d96d16fa95b3e6f7baed3f303d01e962c [21/26] x86/entry: Convert ret_from_fork to C
config: x86_64-randconfig-r023-20210302 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 5de09ef02e24d234d9fc0cd1c6dfe18a1bb784b0)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?id=b529690d96d16fa95b3e6f7baed3f303d01e962c
git remote add luto https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git
git fetch --no-tags luto x86/fixes
git checkout b529690d96d16fa95b3e6f7baed3f303d01e962c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/entry/common.c:217:24: warning: no previous prototype for function 'ret_from_fork' [-Wmissing-prototypes]
__visible void noinstr ret_from_fork(struct task_struct *prev,
^
arch/x86/entry/common.c:217:11: note: declare 'static' if the function is not intended to be used outside of this translation unit
__visible void noinstr ret_from_fork(struct task_struct *prev,
^
static
1 warning generated.
vim +/ret_from_fork +217 arch/x86/entry/common.c
216
> 217 __visible void noinstr ret_from_fork(struct task_struct *prev,
218 int (*kernel_thread_fn)(void *),
219 void *kernel_thread_arg,
220 struct pt_regs *user_regs)
221 {
222 instrumentation_begin();
223
224 schedule_tail(prev);
225
226 if (kernel_thread_fn) {
227 kernel_thread_fn(kernel_thread_arg);
228 user_regs->ax = 0;
229 }
230
231 instrumentation_end();
232 syscall_exit_to_user_mode(user_regs);
233 }
234
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35389 bytes --]
reply other threads:[~2021-03-02 8:16 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=202103021643.DYcErR4a-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.