From: kbuild test robot <lkp@intel.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 48/283] mm/kasan/common.c:481:17: error: 'KASAN_SHADOW_INIT' undeclared; did you mean 'KASAN_SHADOW_END'?
Date: Wed, 5 Dec 2018 12:52:01 +0800 [thread overview]
Message-ID: <201812051256.eEMKJAdG%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 1b1ce5151f3dd9a5bc989207ac56e96dcb84bef4
commit: e76ec930bbe0906735fa147736ab051a8e256b1b [48/283] kasan: initialize shadow to 0xff for tag-based mode
config: x86_64-randconfig-x013-12041647 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout e76ec930bbe0906735fa147736ab051a8e256b1b
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
mm/kasan/common.c: In function 'kasan_module_alloc':
>> mm/kasan/common.c:481:17: error: 'KASAN_SHADOW_INIT' undeclared (first use in this function); did you mean 'KASAN_SHADOW_END'?
__memset(ret, KASAN_SHADOW_INIT, shadow_size);
^~~~~~~~~~~~~~~~~
KASAN_SHADOW_END
mm/kasan/common.c:481:17: note: each undeclared identifier is reported only once for each function it appears in
vim +481 mm/kasan/common.c
459
460 int kasan_module_alloc(void *addr, size_t size)
461 {
462 void *ret;
463 size_t scaled_size;
464 size_t shadow_size;
465 unsigned long shadow_start;
466
467 shadow_start = (unsigned long)kasan_mem_to_shadow(addr);
468 scaled_size = (size + KASAN_SHADOW_MASK) >> KASAN_SHADOW_SCALE_SHIFT;
469 shadow_size = round_up(scaled_size, PAGE_SIZE);
470
471 if (WARN_ON(!PAGE_ALIGNED(shadow_start)))
472 return -EINVAL;
473
474 ret = __vmalloc_node_range(shadow_size, 1, shadow_start,
475 shadow_start + shadow_size,
476 GFP_KERNEL,
477 PAGE_KERNEL, VM_NO_GUARD, NUMA_NO_NODE,
478 __builtin_return_address(0));
479
480 if (ret) {
> 481 __memset(ret, KASAN_SHADOW_INIT, shadow_size);
482 find_vm_area(addr)->flags |= VM_KASAN;
483 kmemleak_ignore(ret);
484 return 0;
485 }
486
487 return -ENOMEM;
488 }
489
---
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: 28949 bytes --]
next reply other threads:[~2018-12-05 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 4:52 kbuild test robot [this message]
2018-12-06 10:13 ` Andrey Konovalov
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=201812051256.eEMKJAdG%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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