From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, kent.overstreet@linux.dev,
roman.gushchin@linux.dev, cl@linux.com, rientjes@google.com,
harry.yoo@oracle.com, souravpanda@google.com,
pasha.tatashin@soleen.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] slab: ensure slab->obj_exts is clear in a newly allocated slab page
Date: Mon, 14 Apr 2025 12:24:08 +0200 [thread overview]
Message-ID: <32eb2a11-2079-450b-a34c-ca432f416500@suse.cz> (raw)
In-Reply-To: <CAJuCfpGrJNiDWxsD=53ZOzWKHAh=xw2pGidg6oAgwj8mETGPQQ@mail.gmail.com>
On 4/11/25 19:45, Suren Baghdasaryan wrote:
> On Fri, Apr 11, 2025 at 9:59 AM Suren Baghdasaryan <surenb@google.com> wrote:
>
> Kent asked me to forward this (his email is misbehaving for some reason):
>
> Yes, ktest doesn't flip on CONFIG_MEMCG.
>
> Those checks you're talking about are also behind CONFIG_DEBUG_VM,
> which isn't normally on. I did do some runs with it on and it didn't
Hm yes I forgot we moved them to be DEBUG_VM or debug_pagealloc only.
> fire - only additional asserts Suren and I added - so something's
> missing.
>
> In the meantime, this needs to go in quickly as a hotfix because it's
> a 6.15-rc1 regression, and I've been getting distros to enable memory
> allocation profiling and I'd be shocked if it doesn't cause memcg
> crashes as well.
I'll send it this week so rc3.
prev parent reply other threads:[~2025-04-14 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 15:57 Suren Baghdasaryan
2025-04-11 16:26 ` Vlastimil Babka
2025-04-11 16:59 ` Suren Baghdasaryan
2025-04-11 17:45 ` Suren Baghdasaryan
2025-04-14 10:24 ` Vlastimil Babka [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=32eb2a11-2079-450b-a34c-ca432f416500@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=harry.yoo@oracle.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=souravpanda@google.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.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