From: wangwensheng <wsw9603@163.com>
To: Andrey Konovalov <andreyknvl@gmail.com>
Cc: kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kasan/test: only do kmalloc_double_kzfree for generic mode
Date: Sun, 24 May 2026 11:17:18 +0800 [thread overview]
Message-ID: <9ab33234-34ec-473f-83ea-e5607b18b36f@163.com> (raw)
In-Reply-To: <CA+fCnZcKwsY=QugBgPAV3GzU51oy5=Q8qGXXzOQAXW=M899umQ@mail.gmail.com>
On 5/21/26 02:19, Andrey Konovalov wrote:
> On Sun, May 17, 2026 at 9:17 AM Wang Wensheng <wsw9603@163.com> wrote:
>> kmalloc_double_kzfree() would corrupt kernel memory when the just
>> freed memory were allocated by another thread before the second
>> call to kfree_sensitive().
>>
>> This could not happen in GENERIC mode as it uses quarantine.
> Quite unfortunate to disable this test for HW_TAGS, but I don't see an
> easy way to resolve the issue otherwise.
>
>> Signed-off-by: Wang Wensheng <wsw9603@163.com>
>> ---
>> mm/kasan/kasan_test_c.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/mm/kasan/kasan_test_c.c b/mm/kasan/kasan_test_c.c
>> index 32d06cbf6a31..02e43ccc9f21 100644
>> --- a/mm/kasan/kasan_test_c.c
>> +++ b/mm/kasan/kasan_test_c.c
>> @@ -874,6 +874,12 @@ static void kmalloc_double_kzfree(struct kunit *test)
>> char *ptr;
>> size_t size = 16;
>>
>> + /*
>> + * Only generic KASAN uses quarantine, which could prevent the just freed
>> + * memory from being allocated soon.
>> + */
> Let's reword this to:
>
> With the tag-based KASAN modes, if the memory happens to be
> reallocated between the two frees and the new allocation tag happens
> to match the old one, the second free will cause a memory corruption.
> Resolving https://bugzilla.kernel.org/show_bug.cgi?id=212177 would
> help to deal with this. With Generic KASAN, it's effectively
> impossible for the memory to get reallocated due to the quarantine.
>
Thanks for your nice comment. I have sent a second version.
>> + KASAN_TEST_NEEDS_CONFIG_ON(test, CONFIG_KASAN_GENERIC);
>> +
>> ptr = kmalloc(size, GFP_KERNEL);
>> KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ptr);
>>
>> --
>> 2.43.0
>>
>> --
>> 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@googlegroups.com.
>> To view this discussion visit https://groups.google.com/d/msgid/kasan-dev/20260517071713.353579-1-wsw9603%40163.com.
> With the comment rewording:
>
> Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
prev parent reply other threads:[~2026-05-24 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 7:17 Wang Wensheng
2026-05-20 18:19 ` Andrey Konovalov
2026-05-24 3:17 ` wangwensheng [this message]
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=9ab33234-34ec-473f-83ea-e5607b18b36f@163.com \
--to=wsw9603@163.com \
--cc=andreyknvl@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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
all inboxes | Powered by JetHome®