From: Andrew Morton <akpm@linux-foundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Hao Ge <hao.ge@linux.dev>,
Kent Overstreet <kent.overstreet@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/alloc_tag: clear codetag for pages allocated before page_ext initialization
Date: Thu, 26 Mar 2026 18:34:20 -0700 [thread overview]
Message-ID: <20260326183420.bbcbef02b8d2f3dedc4c4980@linux-foundation.org> (raw)
In-Reply-To: <CAJuCfpHddCffwF6uid_nW8sMAMpJcOiB62BCeGEtoiDYY6rP4g@mail.gmail.com>
On Thu, 26 Mar 2026 18:19:56 -0700 Suren Baghdasaryan <surenb@google.com> wrote:
> >
> > Do people use CONFIG_MEM_ALLOC_PROFILING_DEBUG much? Is a backport
> > really needed?
>
> IMO backport would be good.
OK, thanks, I'll slap a cc:stable on it and keep it in the 7.1.rc1 queue.
I added
"This bug occurs when CONFIG_MEM_ALLOC_PROFILING_DEBUG=y."
somewhere in the changelog but that's pretty lame and could be expanded
upon in a respin.
> >
> > Either way, it seems that this isn't a very urgent issue so I'm
> > inclined to add it to the 7.1-rc1 pile, perhaps with a cc:stable.
> >
> > Please all share your thoughts with me, thanks.
>
> I'm reviewing and testing the patch and there is a race and a couple
> of smaller issues. I'll post a reply later today.
Cool. I was going to keep it in there for mm-new testing (which is
light). But I guess there isn't much value in this so I'll drop v2.
Sashiko had a bunch of nags, but I think you're checking that routinely?
https://sashiko.dev/#/patchset/20260326140554.191996-1-hao.ge%40linux.dev
next prev parent reply other threads:[~2026-03-27 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 14:05 Hao Ge
2026-03-27 1:11 ` Andrew Morton
2026-03-27 1:19 ` Suren Baghdasaryan
2026-03-27 1:34 ` Andrew Morton [this message]
2026-03-27 1:50 ` Suren Baghdasaryan
2026-03-27 8:14 ` Hao Ge
2026-03-27 4:32 ` Suren Baghdasaryan
2026-03-27 4:39 ` Suren Baghdasaryan
2026-03-27 8:33 ` Hao Ge
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=20260326183420.bbcbef02b8d2f3dedc4c4980@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hao.ge@linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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