From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 4951/14215] usr/include/linux/ptrace.h:76: warning: "PTRACE_GET_SYSCALL_INFO" redefined
Date: Tue, 22 Mar 2022 23:05:44 +0800 [thread overview]
Message-ID: <202203222228.Jqi46omO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f8833a2b23562be2dae91775127c8014c44d8566
commit: b5caa8dd9cc8ad5126f06e9266c326d38a1fc6d2 [4951/14215] samples/seccomp: Improve arch hints
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220322/202203222228.Jqi46omO-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b5caa8dd9cc8ad5126f06e9266c326d38a1fc6d2
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 b5caa8dd9cc8ad5126f06e9266c326d38a1fc6d2
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash samples/
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 >>):
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:50: warning: "PTRACE_GETREGSET" redefined
50 | #define PTRACE_GETREGSET 0x4204
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:153: note: this is the location of the previous definition
153 | #define PTRACE_GETREGSET PTRACE_GETREGSET
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:51: warning: "PTRACE_SETREGSET" redefined
51 | #define PTRACE_SETREGSET 0x4205
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:157: note: this is the location of the previous definition
157 | #define PTRACE_SETREGSET PTRACE_SETREGSET
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:53: warning: "PTRACE_SEIZE" redefined
53 | #define PTRACE_SEIZE 0x4206
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:162: note: this is the location of the previous definition
162 | #define PTRACE_SEIZE PTRACE_SEIZE
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:54: warning: "PTRACE_INTERRUPT" redefined
54 | #define PTRACE_INTERRUPT 0x4207
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:166: note: this is the location of the previous definition
166 | #define PTRACE_INTERRUPT PTRACE_INTERRUPT
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:55: warning: "PTRACE_LISTEN" redefined
55 | #define PTRACE_LISTEN 0x4208
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:170: note: this is the location of the previous definition
170 | #define PTRACE_LISTEN PTRACE_LISTEN
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:57: warning: "PTRACE_PEEKSIGINFO" redefined
57 | #define PTRACE_PEEKSIGINFO 0x4209
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:174: note: this is the location of the previous definition
174 | #define PTRACE_PEEKSIGINFO PTRACE_PEEKSIGINFO
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:65: warning: "PTRACE_GETSIGMASK" redefined
65 | #define PTRACE_GETSIGMASK 0x420a
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:178: note: this is the location of the previous definition
178 | #define PTRACE_GETSIGMASK PTRACE_GETSIGMASK
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:66: warning: "PTRACE_SETSIGMASK" redefined
66 | #define PTRACE_SETSIGMASK 0x420b
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:182: note: this is the location of the previous definition
182 | #define PTRACE_SETSIGMASK PTRACE_SETSIGMASK
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:68: warning: "PTRACE_SECCOMP_GET_FILTER" redefined
68 | #define PTRACE_SECCOMP_GET_FILTER 0x420c
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:186: note: this is the location of the previous definition
186 | #define PTRACE_SECCOMP_GET_FILTER PTRACE_SECCOMP_GET_FILTER
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:69: warning: "PTRACE_SECCOMP_GET_METADATA" redefined
69 | #define PTRACE_SECCOMP_GET_METADATA 0x420d
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:190: note: this is the location of the previous definition
190 | #define PTRACE_SECCOMP_GET_METADATA PTRACE_SECCOMP_GET_METADATA
|
In file included from samples/seccomp/dropper.c:29:
>> usr/include/linux/ptrace.h:76: warning: "PTRACE_GET_SYSCALL_INFO" redefined
76 | #define PTRACE_GET_SYSCALL_INFO 0x420e
|
In file included from samples/seccomp/dropper.c:24:
/usr/include/sys/ptrace.h:194: note: this is the location of the previous definition
194 | #define PTRACE_GET_SYSCALL_INFO PTRACE_GET_SYSCALL_INFO
|
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-03-22 15:06 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=202203222228.Jqi46omO-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.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