From: kernel test robot <lkp@intel.com>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>
Subject: [tip:core/entry 1/1] include/linux/thread_info.h:136:45: error: 'TIF_WORK_SECCOMP' undeclared; did you mean
Date: Wed, 25 Nov 2020 08:33:06 +0800 [thread overview]
Message-ID: <202011250802.zfBrPYwE-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3390 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core/entry
head: 0395124a2fbff5132afee5767071ebe7e05885ac
commit: 0395124a2fbff5132afee5767071ebe7e05885ac [1/1] entry: Fix boot for !CONFIG_GENERIC_ENTRY
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 9.3.0
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
# https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=0395124a2fbff5132afee5767071ebe7e05885ac
git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
git fetch --no-tags tip core/entry
git checkout 0395124a2fbff5132afee5767071ebe7e05885ac
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from arch/xtensa/include/asm/processor.h:15,
from arch/xtensa/kernel/asm-offsets.c:15:
include/linux/seccomp.h: In function 'secure_computing':
>> include/linux/thread_info.h:136:45: error: 'TIF_WORK_SECCOMP' undeclared (first use in this function); did you mean 'TIF_SECCOMP'?
136 | test_ti_thread_flag(current_thread_info(), TIF_WORK_##fl)
| ^~~~~~~~~
include/linux/compiler.h:78:42: note: in definition of macro 'unlikely'
78 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^
include/linux/seccomp.h:45:15: note: in expansion of macro 'test_syscall_work'
45 | if (unlikely(test_syscall_work(SECCOMP)))
| ^~~~~~~~~~~~~~~~~
include/linux/thread_info.h:136:45: note: each undeclared identifier is reported only once for each function it appears in
136 | test_ti_thread_flag(current_thread_info(), TIF_WORK_##fl)
| ^~~~~~~~~
include/linux/compiler.h:78:42: note: in definition of macro 'unlikely'
78 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^
include/linux/seccomp.h:45:15: note: in expansion of macro 'test_syscall_work'
45 | if (unlikely(test_syscall_work(SECCOMP)))
| ^~~~~~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:117: arch/xtensa/kernel/asm-offsets.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1200: prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:185: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
vim +136 include/linux/thread_info.h
132
133 #define set_syscall_work(fl) \
134 set_ti_thread_flag(current_thread_info(), TIF_WORK_##fl)
135 #define test_syscall_work(fl) \
> 136 test_ti_thread_flag(current_thread_info(), TIF_WORK_##fl)
137 #define clear_syscall_work(fl) \
138 clear_ti_thread_flag(current_thread_info(), TIF_WORK_##fl)
139
---
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: 66250 bytes --]
next reply other threads:[~2020-11-25 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 0:33 kernel test robot [this message]
2020-11-25 0:33 kernel test robot
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=202011250802.zfBrPYwE-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=krisman@collabora.com \
--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
all inboxes | Powered by JetHome®