From: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
To: Andrew Morton <akpm@linux-foundation.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Andrey Konovalov <andreyknvl@google.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org
Subject: next-20160314 - KASAN breaks 'make C=2' build...
Date: Tue, 15 Mar 2016 05:11:20 -0400 [thread overview]
Message-ID: <55372.1458033080@turing-police.cc.vt.edu> (raw)
This config breaks sparse:
grep KASAN .config
CONFIG_KASAN_SHADOW_OFFSET=0xdffffc0000000000
CONFIG_HAVE_ARCH_KASAN=y
CONFIG_KASAN=y
# CONFIG_KASAN_OUTLINE is not set
CONFIG_KASAN_INLINE=y
CONFIG_TEST_KASAN=m
LANG=C make C=2
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
DESCEND objtool
CHECK scripts/mod/empty.c
No such file: asan-stack=1
scripts/Makefile.build:291: recipe for target 'scripts/mod/empty.o' failed
make[2]: *** [scripts/mod/empty.o] Error 1
scripts/Makefile.build:440: recipe for target 'scripts/mod' failed
make[1]: *** [scripts/mod] Error 2
Makefile:552: recipe for target 'scripts' failed
make: *** [scripts] Error 2
Looks like it's this chunk from scripts/Makefile.kasan:
CFLAGS_KASAN := $(call cc-option, -fsanitize=kernel-address
-fasan-shadow-offset=$(KASAN_SHADOW_OFFSET)
--param asan-stack=1 --param asan-globals=1
--param asan-instrumentation-with-call-threshold=$(call_threshold))
4AM is a bad time to figure out who's to blame here....
next reply other threads:[~2016-03-15 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 9:11 Valdis Kletnieks [this message]
2016-03-15 9:22 ` Andrey Ryabinin
2016-03-15 11:19 ` Valdis.Kletnieks
2016-03-15 11:33 ` Christopher Li
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=55372.1458033080@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@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
all inboxes | Powered by JetHome®