From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android-trusty-5.4 1/2] warning: include/uapi/linux/trusty/ipc.h: leak CONFIG_COMPAT to user-space
Date: Wed, 23 Sep 2020 13:52:55 +0800 [thread overview]
Message-ID: <202009231351.svakpgpI%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
tree: https://android.googlesource.com/kernel/common android-trusty-5.4
head: 081125c5bf06fa11cb7ca7595de062613bb43c8e
commit: c1ecc4dbc990e05318965f13758670ca8c394640 [1/2] ANDROID: trusty: Move ioctl definitions into uapi
config: x86_64-randconfig-a005-20200923 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project d6ac649ccda289ecc2d2c0cb51892d57e8ec328c)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
git checkout c1ecc4dbc990e05318965f13758670ca8c394640
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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 >>):
>> warning: include/uapi/linux/trusty/ipc.h: leak CONFIG_COMPAT to user-space
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34838 bytes --]
next reply other threads:[~2020-09-23 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 5:52 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-23 4:16 [android-common:android-trusty-5.4 1/2] warning: include/uapi/linux/trusty/ipc.h: leak CONFIG_COMPAT to user-space 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=202009231351.svakpgpI%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.