From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
outbounddisclosures@openai.com, Kyle Zeng <kylebot@openai.com>
Subject: Re: [PATCH 6.12.y] bcachefs: validate disk group parent chains
Date: Fri, 12 Jun 2026 10:41:17 -0400 [thread overview]
Message-ID: <20260612-stable-reply-bcachefs-0004@kernel.org> (raw)
In-Reply-To: <20260611223835.73757-1-kylebot@openai.com>
On Thu, Jun 11, 2026 at 03:38:35PM -0700, Kyle Zeng wrote:
> Reject parent IDs outside the disk-group table, parents that reference
> deleted groups, and cyclic parent chains before the groups are imported.
> This prevents crafted superblocks from making the CPU conversion walk
> past cpu_g->entries.
Thanks for the fix. I can't queue this for stable, though: there's no
upstream commit (bcachefs was removed from mainline after 6.12) and no
maintainer Reviewed-by/Acked-by. I won't take a stable-only change for
a removed subsystem without upstream presence or a maintainer ack.
If you can get Kent to review and ack it, I'll reconsider.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-12 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 22:38 [PATCH 6.12.y] bcachefs: validate disk group parent chains Kyle Zeng
2026-06-12 14:41 ` Sasha Levin [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=20260612-stable-reply-bcachefs-0004@kernel.org \
--to=sashal@kernel.org \
--cc=kylebot@openai.com \
--cc=outbounddisclosures@openai.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox