[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <832e7424-280c-d5e7-ae61-832f4f0a03b9@huawei.com>
Date: Wed, 9 Mar 2022 14:39:19 +0800
From: "liupeng (DM)" <liupeng256@...wei.com>
To: Marco Elver <elver@...gle.com>
CC: <brendanhiggins@...gle.com>, <glider@...gle.com>,
<dvyukov@...gle.com>, <akpm@...ux-foundation.org>,
<linux-kselftest@...r.kernel.org>, <kunit-dev@...glegroups.com>,
<linux-kernel@...r.kernel.org>, <kasan-dev@...glegroups.com>,
<linux-mm@...ck.org>, <wangkefeng.wang@...wei.com>
Subject: Re: [PATCH 0/3] kunit: fix a UAF bug and do some optimization
Good, I will send a revised series latter.
On 2022/3/9 14:12, Marco Elver wrote:
> On Wed, 9 Mar 2022 at 02:29, 'Peng Liu' via kasan-dev
> <kasan-dev@...glegroups.com> wrote:
>> This series is to fix UAF when running kfence test case test_gfpzero,
>> which is time costly. This UAF bug can be easily triggered by setting
>> CONFIG_KFENCE_DYNAMIC_OBJECTS = 65535. Furthermore, some optimization
>> for kunit tests has been done.
> Yeah, I've observed this problem before, so thanks for fixing.
>
> It's CONFIG_KFENCE_NUM_OBJECTS (not "DYNAMIC") - please fix in all patches.
>
Sorry for this mistake, I will check it in all patches.
>> Peng Liu (3):
>> kunit: fix UAF when run kfence test case test_gfpzero
>> kunit: make kunit_test_timeout compatible with comment
>> kfence: test: try to avoid test_gfpzero trigger rcu_stall
>>
>> lib/kunit/try-catch.c | 3 ++-
>> mm/kfence/kfence_test.c | 3 ++-
>> 2 files changed, 4 insertions(+), 2 deletions(-)
>>
>> --
>> 2.18.0.huawei.25
>>
>> --
>> You received this message because you are subscribed to the Google Groups "kasan-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to kasan-dev+unsubscribe@...glegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/kasan-dev/20220309014705.1265861-1-liupeng256%40huawei.com.
> .
Powered by blists - more mailing lists