From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Sasha Levin <sasha.levin@oracle.com>,
Dmitry Vyukov <dvyukov@google.com>,
Konstantin Khlebnikov <koct9i@gmail.com>
Subject: [LSF/MM TOPIC] The kernel address sanitizer
Date: Thu, 25 Dec 2014 16:01:11 +0400 [thread overview]
Message-ID: <CAPAsAGwn=KcWOgrTHeWCS18jWq2wK0JGJxYDT1Y4RUpim6=OuQ@mail.gmail.com> (raw)
Hello
I'm working on the kernel address sanitizer (KASan) -
http://thread.gmane.org/gmane.linux.kernel.mm/120041
KASan is runtime memory debugger designed to find use-after-free and
out-of-bounds accesses.
Seems we've come to agreement that KASan is useful and deserves to be
in mainline, yet the feedback on patches is poor.
It seems like they are stalled, so I would like to discuss the future
of it. I hope this will help in pushing it forward.
Besides we have ideas for further improvements, like:
* Detecting reads of uninitialized memory.
* Quarantine - delaying reallocation of freed memory to increase
chance of catching use after free bugs.
In combination with DEBUG_PAGEALLOC or slab
poisoning it's useful even without KASan.
* and some more...
Perhaps it's worth to discuss them as well. I'll be able to come up
with some prototype until summit if needed.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-12-25 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-25 12:01 Andrey Ryabinin [this message]
2014-12-25 12:13 ` Dmitry Vyukov
2015-01-13 22:00 ` Dave Hansen
2015-01-14 8:18 ` 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='CAPAsAGwn=KcWOgrTHeWCS18jWq2wK0JGJxYDT1Y4RUpim6=OuQ@mail.gmail.com' \
--to=ryabinin.a.a@gmail.com \
--cc=dvyukov@google.com \
--cc=koct9i@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=sasha.levin@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox