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, labbott@redhat.com, hch@infradead.org,
willy@infradead.org, cl@linux.com,
linux-security-module@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH 6/6] Pmalloc: self-test
Date: Fri, 2 Feb 2018 14:14:10 +0800 [thread overview]
Message-ID: <201802021413.1N8bkxCV%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180130151446.24698-7-igor.stoppa@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2865 bytes --]
Hi Igor,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.15]
[cannot apply to next-20180201]
[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/20180202-123437
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/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=xtensa
All error/warnings (new ones prefixed by >>):
mm/pmalloc-selftest.c: In function 'pmalloc_selftest':
>> mm/pmalloc-selftest.c:43:14: error: implicit declaration of function 'vmalloc'; did you mean 'kvmalloc'? [-Werror=implicit-function-declaration]
var_vmall = vmalloc(SIZE_2);
^~~~~~~
kvmalloc
>> mm/pmalloc-selftest.c:43:12: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
var_vmall = vmalloc(SIZE_2);
^
>> mm/pmalloc-selftest.c:52:2: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
vfree(var_vmall);
^~~~~
kvfree
cc1: some warnings being treated as errors
vim +43 mm/pmalloc-selftest.c
19
20 #define validate_alloc(expected, variable, size) \
21 pr_notice("must be " expected ": %s", \
22 is_pmalloc_object(variable, size) > 0 ? "ok" : "no")
23
24 #define is_alloc_ok(variable, size) \
25 validate_alloc("ok", variable, size)
26
27 #define is_alloc_no(variable, size) \
28 validate_alloc("no", variable, size)
29
30 void pmalloc_selftest(void)
31 {
32 struct gen_pool *pool_unprot;
33 struct gen_pool *pool_prot;
34 void *var_prot, *var_unprot, *var_vmall;
35
36 pr_notice("pmalloc self-test");
37 pool_unprot = pmalloc_create_pool("unprotected", 0);
38 pool_prot = pmalloc_create_pool("protected", 0);
39 BUG_ON(!(pool_unprot && pool_prot));
40
41 var_unprot = pmalloc(pool_unprot, SIZE_1 - 1, GFP_KERNEL);
42 var_prot = pmalloc(pool_prot, SIZE_1, GFP_KERNEL);
> 43 var_vmall = vmalloc(SIZE_2);
44 is_alloc_ok(var_unprot, 10);
45 is_alloc_ok(var_unprot, SIZE_1);
46 is_alloc_ok(var_unprot, PAGE_SIZE);
47 is_alloc_no(var_unprot, SIZE_1 + 1);
48 is_alloc_no(var_vmall, 10);
49
50
51 pfree(pool_unprot, var_unprot);
> 52 vfree(var_vmall);
---
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: 53127 bytes --]
next prev parent reply other threads:[~2018-02-02 6:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 15:14 [RFC PATCH v12 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-01-30 15:14 ` [PATCH 1/6] genalloc: track beginning of allocations Igor Stoppa
2018-01-30 15:14 ` [PATCH 2/6] genalloc: selftest Igor Stoppa
2018-01-30 15:14 ` [PATCH 3/6] struct page: add field for vm_struct Igor Stoppa
2018-02-01 0:00 ` Christopher Lameter
2018-02-01 12:42 ` Igor Stoppa
2018-02-01 21:11 ` Kees Cook
2018-02-02 16:01 ` Igor Stoppa
2018-02-02 18:43 ` Christopher Lameter
2018-02-03 16:13 ` Igor Stoppa
2018-02-05 15:33 ` Christopher Lameter
2018-02-09 11:34 ` Igor Stoppa
2018-02-06 12:37 ` Matthew Wilcox
2018-02-09 13:45 ` Igor Stoppa
2018-01-30 15:14 ` [PATCH 4/6] Protectable Memory Igor Stoppa
2018-02-02 5:41 ` kbuild test robot
2018-02-02 5:53 ` kbuild test robot
2018-01-30 15:14 ` [PATCH 5/6] Documentation for Pmalloc Igor Stoppa
2018-01-30 17:08 ` Jonathan Corbet
2018-02-02 15:56 ` Igor Stoppa
2018-02-10 3:37 ` Matthew Wilcox
2018-02-12 15:28 ` Jonathan Corbet
2018-01-30 15:14 ` [PATCH 6/6] Pmalloc: self-test Igor Stoppa
2018-02-02 6:14 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-24 17:56 [RFC PATCH v11 0/6] mm: security: ro protection for dynamic data Igor Stoppa
2018-01-24 17:56 ` [PATCH 6/6] Pmalloc: self-test Igor Stoppa
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=201802021413.1N8bkxCV%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=cl@linux.com \
--cc=hch@infradead.org \
--cc=igor.stoppa@huawei.com \
--cc=jglisse@redhat.com \
--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=willy@infradead.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