[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <572737FB.2020405@emindsoft.com.cn>
Date: Mon, 02 May 2016 19:20:27 +0800
From: Chen Gang <chengang@...ndsoft.com.cn>
To: Alexander Potapenko <glider@...gle.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Dmitriy Vyukov <dvyukov@...gle.com>,
kasan-dev <kasan-dev@...glegroups.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Chen Gang <gang.chen.5i5j@...il.com>
Subject: Re: [PATCH] include/linux/kasan.h: Notice about 0 for kasan_[dis/en]able_current()
On 5/2/16 18:49, Alexander Potapenko wrote:
> On Mon, May 2, 2016 at 7:35 AM, <chengang@...ndsoft.com.cn> wrote:
>>
>> According to their comments and the kasan_depth's initialization, if
>> kasan_depth is zero, it means disable. So kasan_depth need consider
>> about the 0 overflow.
>>
>> Also remove useless comments for dummy kasan_slab_free().
>>
>> Signed-off-by: Chen Gang <gang.chen.5i5j@...il.com>
>
> Acked-by: Alexander Potapenko <glider@...gle.com>
>
OK, thanks.
Another patch thread is also related with this patch thread, please help
check.
And sorry, originally, I did not let the 2 patches in one patches set.
Thanks.
--
Chen Gang (陈刚)
Managing Natural Environments is the Duty of Human Beings.
Powered by blists - more mailing lists