From: <yee.lee@mediatek.com>
To: <linux-kernel@vger.kernel.org>
Cc: <nicholas.Tang@mediatek.com>, <Kuan-Ying.lee@mediatek.com>,
<chinwen.chang@mediatek.com>, Yee Lee <yee.lee@mediatek.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: [PATCH v6 0/2] kasan: solve redzone overwritten issue at debug
Date: Mon, 5 Jul 2021 18:32:25 +0800 [thread overview]
Message-ID: <20210705103229.8505-1-yee.lee@mediatek.com> (raw)
From: Yee Lee <yee.lee@mediatek.com>
Issue: In SLUB debug, hwtag kasan_unpoison() would overwrite the redzone
in those objects with unaligned size.
The first patch Introduces slub_debug_enable_unlikely() to check
the state of debug mode.
The second patch Adds memzero_explict() to separate the initialization for
such condition. The new code path is executed about 1.1% during nromal
booting process. The penalty is acceptable since it only works in debug
mode.
=============
Exp: QEMUv5.2(+mte)/SLUB_debug mode
code path exec : 941/80854 (1.1%)
Changed since v6:
- Move helper instead of introducing a new one.
Changed since v5:
- Fix format
Changed since v4:
- Introduce slub_debug_enable_unlikly() to check the debug state.
- Include "slab.h" and Add slub_debug_enable_unlikly() to lead
the condition statement.
- Add comment block about this new code path in source code.
Changed since v3:
- Apply IS_ENABLED to wrap codes under SLUB debug mode.
- Replace memset() by memzero_explict().
---
Marco Elver (1):
mm: move helper to check slub_debug_enabled
Yee Lee (1):
kasan: Add memzero int for unaligned size at DEBUG
mm/kasan/kasan.h | 12 ++++++++++++
mm/slab.h | 15 +++++++++++----
mm/slub.c | 14 --------------
3 files changed, 23 insertions(+), 18 deletions(-)
--
2.18.0
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next reply other threads:[~2021-07-05 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 10:32 yee.lee [this message]
2021-07-05 10:32 ` [PATCH v6 1/2] mm: move helper to check slub_debug_enabled yee.lee
2021-07-05 10:32 ` [PATCH v6 2/2] kasan: Add memzero int for unaligned size at DEBUG yee.lee
2021-07-05 10:45 ` Marco Elver
2021-07-05 11:12 ` Andrey Konovalov
2021-07-05 11:18 ` Marco Elver
2021-07-05 11:23 ` Andrey Konovalov
2021-07-05 13:53 ` Yee Lee
2021-07-05 11:23 ` 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=20210705103229.8505-1-yee.lee@mediatek.com \
--to=yee.lee@mediatek.com \
--cc=Kuan-Ying.lee@mediatek.com \
--cc=chinwen.chang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nicholas.Tang@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