All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuan-Ying Lee <kylee0686026@gmail.com>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
	Alexander Potapenko <glider@google.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Walter Wu <walter-zh.wu@mediatek.com>,
	Kuan-Ying Lee <kylee0686026@gmail.com>
Subject: [PATCH 0/1] kasan: add memory corruption identification for hardware tag-based
Date: Sun, 30 May 2021 12:47:07 +0800	[thread overview]
Message-ID: <20210530044708.7155-1-kylee0686026@gmail.com> (raw)

This patch is for hardware tag-based kasan to make a good guess
on the kasan bug. Report kasan bug is slab out-of-bound or
use-after-free. Refer to software tag-based kasan detection
mechanism.

Kuan-Ying Lee (1):
  kasan: add memory corruption identification for hardware tag-based
    mode

 lib/Kconfig.kasan         |  8 ++++++++
 mm/kasan/hw_tags.c        | 25 ++++++++++++++++++++++---
 mm/kasan/kasan.h          |  4 ++--
 mm/kasan/report_hw_tags.c | 28 ++++++++++++++++++++++++++++
 4 files changed, 60 insertions(+), 5 deletions(-)

-- 
2.17.1


             reply	other threads:[~2021-05-30  4:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30  4:47 Kuan-Ying Lee [this message]
2021-05-30  4:47 ` [PATCH 1/1] kasan: add memory corruption identification for hardware tag-based mode Kuan-Ying Lee
2021-05-31  8:50   ` Marco Elver
2021-05-31 15:59     ` Kuan-Ying Lee
2021-06-02 12:29       ` Andrey Konovalov
2021-06-02 12:29         ` Andrey Konovalov
2021-06-02 12:24     ` Andrey Konovalov
2021-06-02 12:24       ` Andrey Konovalov

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=20210530044708.7155-1-kylee0686026@gmail.com \
    --to=kylee0686026@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryabinin.a.a@gmail.com \
    --cc=walter-zh.wu@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.