From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>, Josef Bacik <josef@toxicpanda.com>
Subject: Re: Please apply e1b849cfa6b61f1c866a908c9e8dd9b5aaab820b to 6.12.y
Date: Sat, 13 Jun 2026 10:51:30 -0400 [thread overview]
Message-ID: <20260613143004.0005-1-sashal@kernel.org> (raw)
In-Reply-To: <20260612212134.GA3841315@perftesting>
On Fri, Jun 12, 2026 at 05:21:34PM -0400, Josef Bacik wrote:
> AUTOSEL already grabbed the other two patches in this series, but this one is
> equally important and we're currently hitting problems in production without
> this patch. It applies cleanly to 6.12.y. Thanks,
Queued for 6.12.y, thanks.
Note that e1b849cfa6b6 introduced a use-after-free in
inode_switch_wbs_work_fn() that was fixed later by 6689f01d6740
("writeback: Fix use after free in inode_switch_wbs_work_fn()", which
carries Fixes: e1b849cfa6b6 and Cc: stable). That fix wasn't in 6.12.y
yet either, so I've queued it on top to avoid reintroducing the UAF.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-13 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 21:21 Please apply e1b849cfa6b61f1c866a908c9e8dd9b5aaab820b to 6.12.y Josef Bacik
2026-06-13 14:51 ` 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=20260613143004.0005-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=josef@toxicpanda.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