From: Muchun Song <muchun.song@linux.dev>
To: Peng Zhang <zhangpeng.00@bytedance.com>
Cc: kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, dvyukov@google.com,
roman.gushchin@linux.dev, jannh@google.com, sjpark@amazon.de,
akpm@linux-foundation.org, elver@google.com, glider@google.com,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH] mm: kfence: fix PG_slab and memcg_data clearing
Date: Tue, 21 Mar 2023 15:04:46 +0800 [thread overview]
Message-ID: <c22e1d58-e16f-fde5-cee7-c13dedbe1656@linux.dev> (raw)
In-Reply-To: <974ef73e-ab4f-7b24-d070-c981654e8c22@bytedance.com>
On 2023/3/21 12:14, Peng Zhang wrote:
>
> 在 2023/3/20 11:00, Muchun Song 写道:
>> It does not reset PG_slab and memcg_data when KFENCE fails to initialize
>> kfence pool at runtime. It is reporting a "Bad page state" message when
>> kfence pool is freed to buddy. The checking of whether it is a compound
>> head page seems unnecessary sicne we already guarantee this when
>> allocating
>> kfence pool, removing the check to simplify the code.
>>
>> Fixes: 0ce20dd84089 ("mm: add Kernel Electric-Fence infrastructure")
>> Fixes: 8f0b36497303 ("mm: kfence: fix objcgs vector allocation")
>> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
>> ---
>> mm/kfence/core.c | 30 +++++++++++++++---------------
>> 1 file changed, 15 insertions(+), 15 deletions(-)
>>
>> diff --git a/mm/kfence/core.c b/mm/kfence/core.c
>> index 79c94ee55f97..d66092dd187c 100644
>> --- a/mm/kfence/core.c
>> +++ b/mm/kfence/core.c
>> @@ -561,10 +561,6 @@ static unsigned long kfence_init_pool(void)
>> if (!i || (i % 2))
>> continue;
>> - /* Verify we do not have a compound head page. */
>> - if (WARN_ON(compound_head(&pages[i]) != &pages[i]))
>> - return addr;
>> -
>> __folio_set_slab(slab_folio(slab));
>> #ifdef CONFIG_MEMCG
>> slab->memcg_data = (unsigned long)&kfence_metadata[i / 2 -
>> 1].objcg |
>> @@ -597,12 +593,26 @@ static unsigned long kfence_init_pool(void)
>> /* Protect the right redzone. */
>> if (unlikely(!kfence_protect(addr + PAGE_SIZE)))
>> - return addr;
>> + goto reset_slab;
>> addr += 2 * PAGE_SIZE;
>> }
>> return 0;
>> +
>> +reset_slab:
>> + for (i = 0; i < KFENCE_POOL_SIZE / PAGE_SIZE; i++) {
>> + struct slab *slab = page_slab(&pages[i]);
>> +
>> + if (!i || (i % 2))
>> + continue;
>> +#ifdef CONFIG_MEMCG
>> + slab->memcg_data = 0;
>> +#endif
>> + __folio_clear_slab(slab_folio(slab));
>> + }
> Can this loop be simplified to this?
>
> for (i = 2; i < KFENCE_POOL_SIZE / PAGE_SIZE; i+=2) {
> struct slab *slab = page_slab(&pages[i]);
> #ifdef CONFIG_MEMCG
> slab->memcg_data = 0;
> #endif
> __folio_clear_slab(slab_folio(slab));
> }
>
It's a good simplification. The loop setting Pg_slab before this
also can be simplified in the same way. However, I choose a
consistent way to fix this bug. I'd like to send a separate
simplification patch to simplify both two loops instead of
in a bugfix patch.
Thanks.
prev parent reply other threads:[~2023-03-21 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 3:00 Muchun Song
2023-03-20 21:29 ` Andrew Morton
2023-03-21 3:03 ` Muchun Song
2023-03-21 4:14 ` Peng Zhang
2023-03-21 7:04 ` Muchun Song [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=c22e1d58-e16f-fde5-cee7-c13dedbe1656@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=roman.gushchin@linux.dev \
--cc=sjpark@amazon.de \
--cc=songmuchun@bytedance.com \
--cc=zhangpeng.00@bytedance.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