From: Michael Ellerman <mpe@ellerman.id.au>
To: keescook@chromium.org
Cc: kernel-hardening@lists.openwall.com, linux-kernel@vger.kernel.org
Subject: Re: [kernel-hardening] Re: [PATCH] lkdtm: Add tests for LIST_POISON and ZERO_SIZE_PTR
Date: Thu, 17 Nov 2016 21:53:31 +1100 [thread overview]
Message-ID: <87bmxextqs.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <201611160623.afRvXZ5d%fengguang.wu@intel.com>
kbuild test robot <lkp@intel.com> writes:
> [auto build test ERROR on char-misc/char-misc-testing]
> [also build test ERROR on v4.9-rc5]
> [cannot apply to next-20161115]
> [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/Michael-Ellerman/lkdtm-Add-tests-for-LIST_POISON-and-ZERO_SIZE_PTR/20161115-235441
> config: i386-randconfig-i0-201646 (attached as .config)
> compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "mmap_min_addr" [drivers/misc/lkdtm.ko] undefined!
I couldn't see what was causing this, but of course it's just that
mmap_min_addr is not exported, and in that config LKDTM is a module.
I always build it in which is why I didn't notice.
I'm not sure we want to EXPORT_SYMBOL mmap_min_addr just for this test
do we? I could change the test to use mmap_min_addr if LKDTM is
built-in, and otherwise just map at zero. Dunno.
cheers
next prev parent reply other threads:[~2016-11-17 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 10:59 [PATCH] lkdtm: Add tests for LIST_POISON and ZERO_SIZE_PTR Michael Ellerman
2016-11-15 16:25 ` kbuild test robot
2016-11-15 18:02 ` Kees Cook
2016-11-15 22:33 ` kbuild test robot
2016-11-17 10:53 ` Michael Ellerman [this message]
2016-11-17 19:56 ` [kernel-hardening] " Kees Cook
2016-11-18 2:37 ` Michael Ellerman
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=87bmxextqs.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).