From: Thomas Gleixner <tglx@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugobjects: skip activate fixup when disabled by a concurrent OOM
Date: Sun, 28 Jun 2026 18:52:47 +0200 [thread overview]
Message-ID: <87ik72hajk.ffs@fw13> (raw)
In-Reply-To: <20260627230105.0989abc510ad6e5cf63a862c@linux-foundation.org>
On Sat, Jun 27 2026 at 23:01, Andrew Morton wrote:
> On Wed, 10 Jun 2026 11:47:25 +0800 Jiayuan Chen <jiayuan.chen@linux.dev> wrote:
> The patch was sent at an inopportune time - late in -rc people aren't
> paying much attention to new material so bugfixes can fall through
> cracks.
Indeed I missed it somehow.
> If it is known that this WARN can trigger in real-world situations then
> we'll probably want to fix earlier kernels, which means a Fixes: and a
> cc:stable.
It's already fixed upstream:
b81dde13cc16 ("debugobjects: Plug race against a concurrent OOM disable")
syzbot triggered the problem...
prev parent reply other threads:[~2026-06-28 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 3:47 [PATCH] debugobjects: skip activate fixup when disabled by a concurrent OOM Jiayuan Chen
2026-06-28 6:01 ` Andrew Morton
2026-06-28 16:52 ` Thomas Gleixner [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=87ik72hajk.ffs@fw13 \
--to=tglx@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jiayuan.chen@linux.dev \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.