From: kernel test robot <lkp@intel.com>
To: Xiaoming Ni <nixiaoming@huawei.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>
Subject: [mcgrof-next:20211116-sysctl-cleanups-v4 3/35] kernel/hung_task.c:66:28: sparse: sparse: symbol 'sysctl_hung_task_all_cpu_backtrace' was not declared. Should it be static?
Date: Thu, 18 Nov 2021 14:20:31 +0800 [thread overview]
Message-ID: <202111181439.tykxEC3r-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2958 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git 20211116-sysctl-cleanups-v4
head: 5347239461f25fc50aa761923245b9ec4a4aafec
commit: e854631643628749ab037f54ca9c26d69ffabb3e [3/35] hung_task: Move hung_task sysctl interface to hung_task.c
config: i386-randconfig-s002-20211117 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/commit/?id=e854631643628749ab037f54ca9c26d69ffabb3e
git remote add mcgrof-next https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git
git fetch --no-tags mcgrof-next 20211116-sysctl-cleanups-v4
git checkout e854631643628749ab037f54ca9c26d69ffabb3e
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
kernel/hung_task.c:31:19: sparse: sparse: symbol 'sysctl_hung_task_check_count' was not declared. Should it be static?
kernel/hung_task.c:50:29: sparse: sparse: symbol 'sysctl_hung_task_check_interval_secs' was not declared. Should it be static?
kernel/hung_task.c:52:19: sparse: sparse: symbol 'sysctl_hung_task_warnings' was not declared. Should it be static?
>> kernel/hung_task.c:66:28: sparse: sparse: symbol 'sysctl_hung_task_all_cpu_backtrace' was not declared. Should it be static?
kernel/hung_task.c:76:28: sparse: sparse: symbol 'sysctl_hung_task_panic' was not declared. Should it be static?
>> kernel/hung_task.c:282:52: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected void * @@ got void [noderef] __user *buffer @@
kernel/hung_task.c:282:52: sparse: expected void *
kernel/hung_task.c:282:52: sparse: got void [noderef] __user *buffer
>> kernel/hung_task.c:332:35: sparse: sparse: incorrect type in initializer (incompatible argument 3 (different address spaces)) @@ expected int ( [usertype] *proc_handler )( ... ) @@ got int ( * )( ... ) @@
kernel/hung_task.c:332:35: sparse: expected int ( [usertype] *proc_handler )( ... )
kernel/hung_task.c:332:35: sparse: got int ( * )( ... )
kernel/hung_task.c:340:35: sparse: sparse: incorrect type in initializer (incompatible argument 3 (different address spaces)) @@ expected int ( [usertype] *proc_handler )( ... ) @@ got int ( * )( ... ) @@
kernel/hung_task.c:340:35: sparse: expected int ( [usertype] *proc_handler )( ... )
kernel/hung_task.c:340:35: sparse: got int ( * )( ... )
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37291 bytes --]
next reply other threads:[~2021-11-18 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 6:20 kernel test robot [this message]
2021-11-18 6:20 ` [RFC PATCH mcgrof-next] hung_task: sysctl_hung_task_all_cpu_backtrace can be static kernel test robot
2021-11-18 16:32 ` Luis Chamberlain
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=202111181439.tykxEC3r-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nixiaoming@huawei.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
all inboxes | Powered by JetHome®