linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kuthonuzo Luruo <kuthonuzo.luruo@hpe.com>
To: aryabinin@virtuozzo.com, glider@google.com, dvyukov@google.com,
	cl@linux.com, penberg@kernel.org, rientjes@google.com,
	iamjoonsoo.kim@lge.com, akpm@linux-foundation.org
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, kuthonuzo.luruo@hpe.com
Subject: [PATCH v2 0/2] KASAN double-free detection
Date: Fri, 6 May 2016 17:08:41 +0530	[thread overview]
Message-ID: <20160506113841.GA23545@cherokee.in.rdlabs.hpecorp.net> (raw)

First patch provides more reliable double-free detection for KASAN. Review
comments and suggestions from Dmitry Vyukov incorporated. Thanks, Dmitry!

Second patch provides a new concurrent double-free test for 'test_kasan'.

New patchset created from initial version "[PATCH] kasan: improve KASAN
double-free detection". v1 link: https://lkml.org/lkml/2016/5/2/147

SLAB maintainers added to "To:" because of change in mm/slab.c.

Kuthonuzo Luruo (2):
  mm, kasan: improve double-free detection
  kasan: add kasan_double_free() test

 include/linux/kasan.h |    8 +++
 lib/test_kasan.c      |   79 +++++++++++++++++++++++++++++++++
 mm/kasan/kasan.c      |  118 ++++++++++++++++++++++++++++++++++++-------------
 mm/kasan/kasan.h      |   15 +++++-
 mm/kasan/quarantine.c |    7 +++-
 mm/kasan/report.c     |   31 +++++++++++--
 mm/slab.c             |    1 +
 7 files changed, 221 insertions(+), 38 deletions(-)

--
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>

                 reply	other threads:[~2016-05-06 11:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160506113841.GA23545@cherokee.in.rdlabs.hpecorp.net \
    --to=kuthonuzo.luruo@hpe.com \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=cl@linux.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).