From: kbuild test robot <lkp@intel.com>
To: Igor Stoppa <igor.stoppa@huawei.com>
Cc: kbuild-all@01.org, keescook@chromium.org, mhocko@kernel.org,
jmorris@namei.org, labbott@redhat.com,
penguin-kernel@I-love.SAKURA.ne.jp, paul@paul-moore.com,
sds@tycho.nsa.gov, casey@schaufler-ca.com, hch@infradead.org,
linux-security-module@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Igor Stoppa <igor.stoppa@gmail.com>
Subject: Re: [PATCH 1/3] Protectable memory support
Date: Tue, 27 Jun 2017 11:55:06 +0800 [thread overview]
Message-ID: <201706271120.I5LWa6tp%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170626144116.27599-2-igor.stoppa@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
Hi Igor,
[auto build test WARNING on mmotm/master]
[also build test WARNING on v4.12-rc7 next-20170626]
[cannot apply to linus/master linux/master]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Igor-Stoppa/ro-protection-for-dynamic-data/20170627-103230
base: git://git.cmpxchg.org/linux-mmotm.git master
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=powerpc
All warnings (new ones prefixed by >>):
warning: (ARCH_HAS_SET_MEMORY && CPM && TEE && SGI_XP && SRAM && CAIF_VIRTIO && FSL_FMAN && MVNETA_BM && VIDEO_CODA && FB_SH_MOBILE_MERAM && INFINIBAND_CXGB3 && INFINIBAND_CXGB4 && INFINIBAND_I40IW && MMP_TDMA && UIO_PRUSS && ION && FSL_PAMU && FSL_DPAA && QUICC_ENGINE) selects GENERIC_ALLOCATOR which has unmet direct dependencies (ARCH_HAS_SET_MEMORY)
---
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: 54313 bytes --]
next prev parent reply other threads:[~2017-06-27 3:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 14:41 [PATCH v7 0/3] ro protection for dynamic data Igor Stoppa
2017-06-26 14:41 ` [PATCH 1/3] Protectable memory support Igor Stoppa
2017-06-27 3:17 ` kbuild test robot
2017-06-27 3:55 ` kbuild test robot [this message]
2017-06-26 14:41 ` [PATCH 2/3] LSM: Convert security_hook_heads into explicit array of struct list_head Igor Stoppa
2017-06-26 14:41 ` [PATCH 3/3] Make LSM Writable Hooks a command line option Igor Stoppa
2017-06-27 5:07 ` kbuild test robot
2017-06-27 6:48 ` kbuild test robot
2017-06-29 2:26 ` 7361ce7529: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h kernel test robot
2017-06-27 17:33 [PATCH v8 0/3] mm: LSM: ro protection for dynamic data Igor Stoppa
2017-06-27 17:33 ` [PATCH 1/3] Protectable memory support Igor Stoppa
2017-07-05 13:46 [PATCH v9 0/3] mm: security: ro protection for dynamic data Igor Stoppa
2017-07-05 13:46 ` [PATCH 1/3] Protectable memory support Igor Stoppa
2017-07-06 16:27 ` Jerome Glisse
2017-07-07 8:42 ` Igor Stoppa
2017-07-07 18:48 ` Jerome Glisse
2017-07-10 15:15 ` Igor Stoppa
2017-07-10 15:06 [PATCH v10 0/3] mm: security: ro protection for dynamic data Igor Stoppa
2017-07-10 15:06 ` [PATCH 1/3] Protectable memory support Igor Stoppa
2017-07-11 2:05 ` kbuild 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=201706271120.I5LWa6tp%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=casey@schaufler-ca.com \
--cc=hch@infradead.org \
--cc=igor.stoppa@gmail.com \
--cc=igor.stoppa@huawei.com \
--cc=jmorris@namei.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sds@tycho.nsa.gov \
/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