Messages in this thread | | | Date | Mon, 20 Mar 2023 14:29:54 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH] mm: kfence: fix PG_slab and memcg_data clearing |
| |
On Mon, 20 Mar 2023 11:00:59 +0800 Muchun Song <songmuchun@bytedance.com> wrote:
> 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>
I'm not sure how the -stable maintainers are to handle two Fixes: tags. Can we narrow it down to one please? I assume 8f0b36497303 triggered the bad_page() warning?
| |