From: kbuild test robot <lkp@intel.com>
To: Micah Morton <mortonm@chromium.org>
Cc: kbuild-all@01.org, linux-security-module@vger.kernel.org,
James Morris <james.morris@microsoft.com>
Subject: [security:next-general 83/85] security/safesetid/lsm.c:17:10: fatal error: asm/syscall.h: No such file or directory
Date: Wed, 30 Jan 2019 08:33:30 +0800 [thread overview]
Message-ID: <201901300828.TveZbnBP%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
head: 2f87324be7736151bd1f9bf1d63b1eb0401011ba
commit: aeca4e2ca65c1aeacfbe520684e6421719d99417 [83/85] LSM: add SafeSetID module that gates setid calls
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gnu-gcc (Debian 8.2.0-11) 8.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout aeca4e2ca65c1aeacfbe520684e6421719d99417
# save the attached .config to linux build tree
GCC_VERSION=8.2.0 make.cross ARCH=m68k
All errors (new ones prefixed by >>):
>> security/safesetid/lsm.c:17:10: fatal error: asm/syscall.h: No such file or directory
#include <asm/syscall.h>
^~~~~~~~~~~~~~~
compilation terminated.
vim +17 security/safesetid/lsm.c
16
> 17 #include <asm/syscall.h>
18 #include <linux/hashtable.h>
19 #include <linux/lsm_hooks.h>
20 #include <linux/module.h>
21 #include <linux/ptrace.h>
22 #include <linux/sched/task_stack.h>
23 #include <linux/security.h>
24
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 48517 bytes --]
next reply other threads:[~2019-01-30 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 0:33 kbuild test robot [this message]
2019-01-30 15:56 ` [PATCH] LSM: SafeSetID: remove unused include mortonm
2019-01-30 20:30 ` James Morris
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=201901300828.TveZbnBP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=james.morris@microsoft.com \
--cc=kbuild-all@01.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mortonm@chromium.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;
as well as URLs for NNTP newsgroup(s).