From: kbuild test robot <lkp@intel.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: kbuild-all@01.org, keescook@chromium.org,
kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lkdtm: Add tests for LIST_POISON and ZERO_SIZE_PTR
Date: Wed, 16 Nov 2016 00:25:05 +0800 [thread overview]
Message-ID: <201611160036.8vibDrnK%fengguang.wu@intel.com> (raw)
In-Reply-To: <1479207559-8510-1-git-send-email-mpe@ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
Hi Michael,
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING 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-x007-201646 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
drivers/misc/lkdtm_bugs.c: In function 'test_poison_ptr':
>> drivers/misc/lkdtm_bugs.c:178:9: warning: large integer implicitly truncated to unsigned type [-Woverflow]
*ptr = 0xdeadbeefabcd1234;
^~~~~~~~~~~~~~~~~~
vim +178 drivers/misc/lkdtm_bugs.c
162 }
163
164 /*
165 * Creating a mapping and adding mmap_min_addr to the value is cheating
166 * in a way. But it simulates the case where an attacker is able to
167 * cause an access at a small offset from the base value, leading to a
168 * user space access. If an arch doesn't define CONFIG_ILLEGAL_POINTER_VALUE
169 * then it's likely this will work in the absence of other protections.
170 */
171 ptr = mmap_min_addr + base;
172
173 pr_info("attempting read of %s %p\n", desc, ptr);
174 val = *ptr;
175 pr_info("FAIL: Was able to read %s! Got 0x%lx\n", desc, val);
176
177 pr_info("attempting write of %s %p\n", desc, ptr);
> 178 *ptr = 0xdeadbeefabcd1234;
179 pr_info("FAIL: Was able to write %s! Now = 0x%lx\n", desc, *ptr);
180
181 vm_munmap(uaddr, PAGE_SIZE);
182 }
183
184 void lkdtm_ACCESS_LIST_POISON(void)
185 {
186 test_poison_ptr(LIST_POISON1, "LIST_POISON");
---
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: 24141 bytes --]
next prev parent reply other threads:[~2016-11-15 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 10:59 Michael Ellerman
2016-11-15 16:25 ` kbuild test robot [this message]
2016-11-15 18:02 ` Kees Cook
2016-11-15 22:33 ` kbuild test robot
2016-11-17 10:53 ` [kernel-hardening] " Michael Ellerman
2016-11-17 19:56 ` 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=201611160036.8vibDrnK%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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
all inboxes | Powered by JetHome®