From: kbuild test robot <lkp@intel.com>
To: Alexander Potapenko <glider@google.com>
Cc: kbuild-all@01.org, adech.fo@gmail.com, cl@linux.com,
dvyukov@google.com, akpm@linux-foundation.org,
ryabinin.a.a@gmail.com, rostedt@goodmis.org,
iamjoonsoo.kim@lge.com, js1304@gmail.com, kcc@google.com,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 7/7] mm: kasan: Initial memory quarantine implementation
Date: Fri, 26 Feb 2016 22:02:51 +0800 [thread overview]
Message-ID: <201602262252.5asayFU6%fengguang.wu@intel.com> (raw)
In-Reply-To: <5770b96c4fbe63c6d439c4e4191766652e38bd1d.1456492360.git.glider@google.com>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
Hi Alexander,
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.5-rc5]
[cannot apply to next-20160226]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Alexander-Potapenko/SLAB-support-for-KASAN/20160226-213301
config: x86_64-randconfig-x006-201608 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
mm/slab.c: In function '__cache_free':
>> mm/slab.c:3384:2: error: implicit declaration of function '___cache_free' [-Werror=implicit-function-declaration]
___cache_free(cachep, objp, caller);
^
mm/slab.c: At top level:
>> mm/slab.c:3387:6: warning: conflicting types for '___cache_free'
void ___cache_free(struct kmem_cache *cachep, void *objp,
^
mm/slab.c:3384:2: note: previous implicit declaration of '___cache_free' was here
___cache_free(cachep, objp, caller);
^
cc1: some warnings being treated as errors
vim +/___cache_free +3384 mm/slab.c
3378 if (kasan_slab_free(cachep, objp))
3379 /* The object has been put into the quarantine, don't touch it
3380 * for now.
3381 */
3382 return;
3383 #endif
> 3384 ___cache_free(cachep, objp, caller);
3385 }
3386
> 3387 void ___cache_free(struct kmem_cache *cachep, void *objp,
3388 unsigned long caller)
3389 {
3390 struct array_cache *ac;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 28175 bytes --]
prev parent reply other threads:[~2016-02-26 14:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:30 [PATCH v3 0/7] SLAB support for KASAN Alexander Potapenko
2016-02-26 13:30 ` Alexander Potapenko
2016-02-26 13:30 ` [PATCH v3 1/7] kasan: Modify kmalloc_large_oob_right(), add kmalloc_pagealloc_oob_right() Alexander Potapenko
2016-02-26 13:30 ` Alexander Potapenko
2016-02-26 13:30 ` [PATCH v3 2/7] mm, kasan: SLAB support Alexander Potapenko
2016-02-26 13:30 ` Alexander Potapenko
2016-02-26 14:30 ` kbuild test robot
2016-02-26 13:30 ` [PATCH v3 3/7] mm, kasan: Added GFP flags to KASAN API Alexander Potapenko
2016-02-26 13:30 ` Alexander Potapenko
2016-02-26 13:51 ` kbuild test robot
2016-02-26 13:30 ` [PATCH v3 4/7] arch, ftrace: For KASAN put hard/soft IRQ entries into separate sections Alexander Potapenko
2016-02-26 13:30 ` Alexander Potapenko
2016-02-26 17:45 ` Steven Rostedt
2016-02-26 17:45 ` Steven Rostedt
2016-02-26 13:30 ` [PATCH v3 5/7] mm, kasan: Stackdepot implementation. Enable stackdepot for SLAB Alexander Potapenko
2016-02-26 13:30 ` Alexander Potapenko
2016-02-26 13:30 ` [PATCH v3 6/7] kasan: Test fix: Warn if the UAF could not be detected in kmalloc_uaf2 Alexander Potapenko
2016-02-26 13:30 ` Alexander Potapenko
2016-02-26 13:30 ` [PATCH v3 7/7] mm: kasan: Initial memory quarantine implementation Alexander Potapenko
2016-02-26 13:30 ` Alexander Potapenko
2016-02-26 14:02 ` kbuild test robot [this message]
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=201602262252.5asayFU6%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=adech.fo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=kbuild-all@01.org \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rostedt@goodmis.org \
--cc=ryabinin.a.a@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.