From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Kees Cook <keescook@chromium.org>
Subject: [tip:x86/entry 10/15] kernel/entry/common.c:58:41: sparse: sparse: too many arguments for function __secure_computing
Date: Mon, 27 Jul 2020 20:06:58 +0800 [thread overview]
Message-ID: <202007272055.pbEfFsJR%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3205 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/entry
head: 72c3c0fe54a3f3ddea8f5ca468ddf9deaf2100b7
commit: 27d6b4d14f5c3ab21c4aef87dd04055a2d7adf14 [10/15] x86/entry: Use generic syscall entry function
config: i386-randconfig-s001-20200727 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-94-geb6779f6-dirty
git checkout 27d6b4d14f5c3ab21c4aef87dd04055a2d7adf14
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
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/entry/common.c:58:41: sparse: sparse: too many arguments for function __secure_computing
vim +58 kernel/entry/common.c
142781e108b13b Thomas Gleixner 2020-07-22 43
142781e108b13b Thomas Gleixner 2020-07-22 44 static long syscall_trace_enter(struct pt_regs *regs, long syscall,
142781e108b13b Thomas Gleixner 2020-07-22 45 unsigned long ti_work)
142781e108b13b Thomas Gleixner 2020-07-22 46 {
142781e108b13b Thomas Gleixner 2020-07-22 47 long ret = 0;
142781e108b13b Thomas Gleixner 2020-07-22 48
142781e108b13b Thomas Gleixner 2020-07-22 49 /* Handle ptrace */
142781e108b13b Thomas Gleixner 2020-07-22 50 if (ti_work & (_TIF_SYSCALL_TRACE | _TIF_SYSCALL_EMU)) {
142781e108b13b Thomas Gleixner 2020-07-22 51 ret = arch_syscall_enter_tracehook(regs);
142781e108b13b Thomas Gleixner 2020-07-22 52 if (ret || (ti_work & _TIF_SYSCALL_EMU))
142781e108b13b Thomas Gleixner 2020-07-22 53 return -1L;
142781e108b13b Thomas Gleixner 2020-07-22 54 }
142781e108b13b Thomas Gleixner 2020-07-22 55
142781e108b13b Thomas Gleixner 2020-07-22 56 /* Do seccomp after ptrace, to catch any tracer changes. */
142781e108b13b Thomas Gleixner 2020-07-22 57 if (ti_work & _TIF_SECCOMP) {
142781e108b13b Thomas Gleixner 2020-07-22 @58 ret = __secure_computing(NULL);
142781e108b13b Thomas Gleixner 2020-07-22 59 if (ret == -1L)
142781e108b13b Thomas Gleixner 2020-07-22 60 return ret;
142781e108b13b Thomas Gleixner 2020-07-22 61 }
142781e108b13b Thomas Gleixner 2020-07-22 62
142781e108b13b Thomas Gleixner 2020-07-22 63 if (unlikely(ti_work & _TIF_SYSCALL_TRACEPOINT))
142781e108b13b Thomas Gleixner 2020-07-22 64 trace_sys_enter(regs, syscall);
142781e108b13b Thomas Gleixner 2020-07-22 65
142781e108b13b Thomas Gleixner 2020-07-22 66 syscall_enter_audit(regs, syscall);
142781e108b13b Thomas Gleixner 2020-07-22 67
142781e108b13b Thomas Gleixner 2020-07-22 68 return ret ? : syscall;
142781e108b13b Thomas Gleixner 2020-07-22 69 }
142781e108b13b Thomas Gleixner 2020-07-22 70
:::::: The code at line 58 was first introduced by commit
:::::: 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 entry: Provide generic syscall entry functionality
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
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: 35948 bytes --]
reply other threads:[~2020-07-27 12:12 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=202007272055.pbEfFsJR%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox