[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210804082230.10837-1-Kuan-Ying.Lee@mediatek.com>
Date: Wed, 4 Aug 2021 16:22:28 +0800
From: Kuan-Ying Lee <Kuan-Ying.Lee@...iatek.com>
To: Nicholas Tang <nicholas.tang@...iatek.com>,
Andrew Yang <andrew.tang@...iatek.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Alexander Potapenko <glider@...gle.com>,
Marco Elver <elver@...gle.com>,
Catalin Marinas <catalin.marinas@....com>,
Chinwen Chang <chinwen.chang@...iatek.com>,
Andrew Morton <akpm@...ux-foundation.org>
CC: <kasan-dev@...glegroups.com>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
Kuan-Ying Lee <Kuan-Ying.Lee@...iatek.com>
Subject: [PATCH v2 0/2] kasan: reset tag when accessing invalid data
With hardware tag-based kasan enabled, we reset the tag
when we access metadata to avoid from false alarm.
Changes since v2:
- Refine the commit message in detail.
- Thanks Andrey's explanation about false alarm
of kmemleak.
Kuan-Ying Lee (2):
kasan, kmemleak: reset tags when scanning block
kasan, slub: reset tag when printing address
mm/kmemleak.c | 6 +++---
mm/slub.c | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
--
2.18.0
Powered by blists - more mailing lists