From: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: <kasan-dev@googlegroups.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <wsd_upstream@mediatek.com>,
<chinwen.chang@mediatek.com>, <nicholas.tang@mediatek.com>,
Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
Subject: [PATCH v4 0/3] kasan: add memory corruption identification support for hw tag-based kasan
Date: Sat, 26 Jun 2021 18:09:28 +0800 [thread overview]
Message-ID: <20210626100931.22794-1-Kuan-Ying.Lee@mediatek.com> (raw)
Add memory corruption identification for hardware tag-based KASAN mode.
Changes since v4:
- Change report_tags.h to report_tags.c
- Refine the commit message
- Test lib/test_kasan module with SW_TAGS mode
- Test lib/test_kasan module with HW_TAGS mode
- Rebase to latest linux-next
Changes since v3:
- Preserve Copyright from hw_tags.c/sw_tags.c and
report_sw_tags.c/report_hw_tags.c
- Make non-trivial change in kasan sw tag-based mode
Changes since v2:
- Thanks for Marco's Suggestion
- Rename the CONFIG_KASAN_SW_TAGS_IDENTIFY
- Integrate tag-based kasan common part
- Rebase to latest linux-next
Kuan-Ying Lee (3):
kasan: rename CONFIG_KASAN_SW_TAGS_IDENTIFY to
CONFIG_KASAN_TAGS_IDENTIFY
kasan: integrate the common part of two KASAN tag-based modes
kasan: add memory corruption identification support for hardware
tag-based mode
lib/Kconfig.kasan | 4 +--
mm/kasan/Makefile | 4 +--
mm/kasan/hw_tags.c | 22 ---------------
mm/kasan/kasan.h | 4 +--
mm/kasan/report_hw_tags.c | 5 ----
mm/kasan/report_sw_tags.c | 43 ----------------------------
mm/kasan/report_tags.c | 51 +++++++++++++++++++++++++++++++++
mm/kasan/sw_tags.c | 41 ---------------------------
mm/kasan/tags.c | 59 +++++++++++++++++++++++++++++++++++++++
9 files changed, 116 insertions(+), 117 deletions(-)
create mode 100644 mm/kasan/report_tags.c
create mode 100644 mm/kasan/tags.c
--
2.18.0
next reply other threads:[~2021-06-26 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 10:09 Kuan-Ying Lee [this message]
2021-06-26 10:09 ` [PATCH v4 1/3] kasan: rename CONFIG_KASAN_SW_TAGS_IDENTIFY to CONFIG_KASAN_TAGS_IDENTIFY Kuan-Ying Lee
2021-06-28 6:00 ` Marco Elver
2021-06-26 10:09 ` [PATCH v4 2/3] kasan: integrate the common part of two KASAN tag-based modes Kuan-Ying Lee
2021-06-26 15:12 ` Andrey Konovalov
2021-06-28 6:00 ` Marco Elver
2021-06-26 10:09 ` [PATCH v4 3/3] kasan: add memory corruption identification support for hardware tag-based mode Kuan-Ying Lee
2021-06-28 6:00 ` Marco Elver
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=20210626100931.22794-1-Kuan-Ying.Lee@mediatek.com \
--to=kuan-ying.lee@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=chinwen.chang@mediatek.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=nicholas.tang@mediatek.com \
--cc=ryabinin.a.a@gmail.com \
--cc=wsd_upstream@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 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).