From: kbuild test robot <lkp@intel.com>
To: Igor Stoppa <igor.stoppa@huawei.com>
Cc: kbuild-all@01.org, jglisse@redhat.com, keescook@chromium.org,
mhocko@kernel.org, jmorris@namei.org,
penguin-kernel@I-love.SAKURA.ne.jp, labbott@redhat.com,
hch@infradead.org, paul@paul-moore.com, sds@tycho.nsa.gov,
casey@schaufler-ca.com, linux-security-module@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Igor Stoppa <igor.stoppa@huawei.com>
Subject: Re: [PATCH 3/3] Make LSM Writable Hooks a command line option
Date: Tue, 11 Jul 2017 12:12:33 +0800 [thread overview]
Message-ID: <201707111218.WdNdnvYN%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170710150603.387-4-igor.stoppa@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
Hi Igor,
[auto build test ERROR on linus/master]
[cannot apply to v4.12]
[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/mm-security-ro-protection-for-dynamic-data/20170711-084116
config: score-spct6600_defconfig (attached as .config)
compiler: score-elf-gcc (GCC) 4.9.1 20140622 (prerelease)
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=score
All errors (new ones prefixed by >>):
security/security.o: In function `security_init':
>> security.c:(.init.text+0x68): undefined reference to `pmalloc_create_pool'
>> security.c:(.init.text+0x98): undefined reference to `pmalloc'
>> security.c:(.init.text+0x150): undefined reference to `pmalloc_protect_pool'
---
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: 7884 bytes --]
next prev parent reply other threads:[~2017-07-11 4:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2017-07-10 15:06 ` [PATCH 2/3] LSM: Convert security_hook_heads into explicit array of struct list_head Igor Stoppa
2017-07-10 15:06 ` [PATCH 3/3] Make LSM Writable Hooks a command line option Igor Stoppa
2017-07-11 4:12 ` kbuild test robot [this message]
2017-07-11 11:12 ` [PATCH v10 0/3] mm: security: ro protection for dynamic data Tetsuo Handa
2017-07-11 11:37 ` Igor Stoppa
-- strict thread matches above, loose matches on Subject: below --
2017-07-05 13:46 [PATCH v9 " Igor Stoppa
2017-07-05 13:46 ` [PATCH 3/3] Make LSM Writable Hooks a command line option Igor Stoppa
2017-06-27 17:33 [PATCH v8 0/3] mm: LSM: ro protection for dynamic data Igor Stoppa
2017-06-27 17:33 ` [PATCH 3/3] Make LSM Writable Hooks a command line option Igor Stoppa
2017-06-27 17:51 ` Christoph Hellwig
2017-06-28 8:25 ` Igor Stoppa
2017-06-26 14:41 [PATCH v7 0/3] ro protection for dynamic data 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
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=201707111218.WdNdnvYN%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=casey@schaufler-ca.com \
--cc=hch@infradead.org \
--cc=igor.stoppa@huawei.com \
--cc=jglisse@redhat.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