[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YN7eXr30zVH7nLhQ@elver.google.com>
Date: Fri, 2 Jul 2021 11:37:34 +0200
From: Marco Elver <elver@...gle.com>
To: yee.lee@...iatek.com
Cc: andreyknvl@...il.com, wsd_upstream@...iatek.com,
nicholas.Tang@...iatek.com, Kuan-Ying.lee@...iatek.com,
chinwen.chang@...iatek.com,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthias Brugger <matthias.bgg@...il.com>,
"open list:KASAN" <kasan-dev@...glegroups.com>,
"open list:MEMORY MANAGEMENT" <linux-mm@...ck.org>,
open list <linux-kernel@...r.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>
Subject: Re: [PATCH v4 2/2] kasan: Add memzero int for unaligned size at DEBUG
On Fri, Jul 02, 2021 at 04:54PM +0800, yee.lee@...iatek.com wrote:
> From: Yee Lee <yee.lee@...iatek.com>
>
> Issue: when SLUB debug is on, hwtag kasan_unpoison() would overwrite
> the redzone of object with unaligned size.
>
> An additional memzero_explicit() path is added to replacing init by
> hwtag instruction for those unaligned size at SLUB debug mode.
>
> The penalty is acceptable since they are only enabled in debug mode,
> not production builds. A block of comment is added for explanation.
>
> ---
> v4:
> - Add "slab.h" header
> - Use slub_debug_enabled_unlikely() to replace IS_ENABLED
> - Refine the comment block
^^ this changelog ...
> ---
^^ this '---' is wrong unfortunately.
> Signed-off-by: Yee Lee <yee.lee@...iatek.com>
> Suggested-by: Marco Elver <elver@...gle.com>
> Suggested-by: Andrey Konovalov <andreyknvl@...il.com>
> Cc: Andrey Ryabinin <ryabinin.a.a@...il.com>
> Cc: Alexander Potapenko <glider@...gle.com>
> Cc: Dmitry Vyukov <dvyukov@...gle.com>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
... should come after the tags.
git am removes anything between the first '---' and the actual patch
from the commit message.
The typical convention is to place the changelog after a '---' _after_
the tags, so that it is removed from the final commit message.
I think the code looks fine now, so please go ahead and send v5.
Thanks,
-- Marco
Powered by blists - more mailing lists