From: Peng Zhang <zhangpeng.00@bytedance.com>
To: Muchun Song <songmuchun@bytedance.com>,
glider@google.com, elver@google.com, dvyukov@google.com,
akpm@linux-foundation.org, sjpark@amazon.de, jannh@google.com,
muchun.song@linux.dev, roman.gushchin@linux.dev
Cc: kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: kfence: fix PG_slab and memcg_data clearing
Date: Tue, 21 Mar 2023 12:14:08 +0800 [thread overview]
Message-ID: <974ef73e-ab4f-7b24-d070-c981654e8c22@bytedance.com> (raw)
In-Reply-To: <20230320030059.20189-1-songmuchun@bytedance.com>
在 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));
}
> +
> + return addr;
> }
>
> static bool __init kfence_init_pool_early(void)
> @@ -632,16 +642,6 @@ static bool __init kfence_init_pool_early(void)
> * fails for the first page, and therefore expect addr==__kfence_pool in
> * most failure cases.
> */
> - for (char *p = (char *)addr; p < __kfence_pool + KFENCE_POOL_SIZE; p += PAGE_SIZE) {
> - struct slab *slab = virt_to_slab(p);
> -
> - if (!slab)
> - continue;
> -#ifdef CONFIG_MEMCG
> - slab->memcg_data = 0;
> -#endif
> - __folio_clear_slab(slab_folio(slab));
> - }
> memblock_free_late(__pa(addr), KFENCE_POOL_SIZE - (addr - (unsigned long)__kfence_pool));
> __kfence_pool = NULL;
> return false;
next prev parent reply other threads:[~2023-03-21 4:14 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 [this message]
2023-03-21 7:04 ` Muchun Song
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=974ef73e-ab4f-7b24-d070-c981654e8c22@bytedance.com \
--to=zhangpeng.00@bytedance.com \
--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=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=sjpark@amazon.de \
--cc=songmuchun@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