From: Nikolay Borisov <n.borisov.lkml@gmail.com>
To: aryabinin@virtuozzo.com
Cc: glider@google.com, Dmitry Vyukov <dvyukov@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: kasan behavior when built with unsupported compiler
Date: Tue, 7 Mar 2017 17:35:42 +0200 [thread overview]
Message-ID: <1eb0b1ba-3847-9bdc-8f4a-adcd34de3486@gmail.com> (raw)
Hello,
I've been chasing a particular UAF as reported by kasan
(https://www.spinics.net/lists/kernel/msg2458136.html). However, one
thing which I took notice of rather lately is that I was building my
kernel with gcc 4.7.4 which is not supported by kasan as indicated by
the following string:
scripts/Makefile.kasan:19: Cannot use CONFIG_KASAN:
-fsanitize=kernel-address is not supported by compiler
Nevertheless, the kernel compiles and when I boot it I see the kasan
splats as per the referenced thread. If, however, I build the kernel
with a newer compiler version 5.4.0 kasan no longer complains.
At this point I'm wondering whether the splats can be due to old
compiler being used e.g. false positives or are they genuine splats and
gcc 5 somehow obfuscates them ? Clearly despite the warning about not
being able to use CONFIG_KASAN it is still working since I'm seeing the
splats. Is this valid behavior ?
Regards,
Nikolay
next reply other threads:[~2017-03-07 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 15:35 Nikolay Borisov [this message]
2017-03-07 15:54 ` Dmitry Vyukov
2017-03-07 16:05 ` Alexander Potapenko
2017-03-07 17:33 ` Nikolay Borisov
2017-03-07 17:51 ` Alexander Potapenko
2017-03-07 20:24 ` Nikolay Borisov
2017-03-07 16:26 ` Andrey Ryabinin
2017-03-07 16:40 ` Dmitry Vyukov
2017-03-08 8:10 ` Nikolay Borisov
2017-03-08 12:34 ` Dmitry Vyukov
2017-03-09 9:46 ` Andrey Ryabinin
2017-03-09 9:47 ` Dmitry Vyukov
2017-03-09 9:58 ` Nikolay Borisov
2017-03-09 10:16 ` Dmitry Vyukov
2017-03-09 11:23 ` Andrey Ryabinin
2017-03-07 16:23 ` Andrey Ryabinin
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=1eb0b1ba-3847-9bdc-8f4a-adcd34de3486@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=linux-kernel@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
Powered by JetHome