linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kuthonuzo Luruo <kuthonuzo.luruo@hpe.com>
To: dvyukov@google.com, aryabinin@virtuozzo.com, glider@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, ynorov@caviumnetworks.com,
	kuthonuzo.luruo@hpe.com
Subject: [PATCH v3 0/2] KASAN double-free detection
Date: Tue, 24 May 2016 23:57:59 +0530	[thread overview]
Message-ID: <20160524182759.GA4747@cherokee.in.rdlabs.hpecorp.net> (raw)

Hello Alexander/Andrey/Dmitry/Reviewers,

Submitting v3 for your review/consideration. First patch provides more
reliable double-free detection for KASAN. Second patch provides new
double-free tests for 'test_kasan'.

Major changes from v2:
o object lock/unlock simplified to use generic bit spinlock apis instead of
  custom CAS loop. A 'safety valve' is provided for lock in case an
  out-of-bounds write flips lock bit.

o test_kasan concurrent double-free test simplified to use
  on_each_cpu_mask() instead of custom threads.
 
v2 link: https://lkml.org/lkml/2016/5/6/210

Patchset is based on linux-next 'next-20160524'.

Thanks,

Kuthonuzo

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

 include/linux/kasan.h |    7 +++-
 lib/test_kasan.c      |   47 ++++++++++++++++++++++++++
 mm/kasan/kasan.c      |   88 ++++++++++++++++++++++++++++++++++---------------
 mm/kasan/kasan.h      |   44 +++++++++++++++++++++++-
 mm/kasan/quarantine.c |    2 +
 mm/kasan/report.c     |   28 ++++++++++++++--
 mm/slab.c             |    3 +-
 mm/slub.c             |    2 +-
 8 files changed, 185 insertions(+), 36 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-24 18:28 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=20160524182759.GA4747@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 \
    --cc=ynorov@caviumnetworks.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