From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: Sasha Levin <sashal@kernel.org>,
harshit.m.mogalapalli@oracle.com, stable@vger.kernel.org,
patches@lists.linux.dev, "Zhou, Yun" <yun.zhou@windriver.com>
Subject: Re: [PATCH 6.12.y] ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT
Date: Sun, 26 Jul 2026 17:24:50 -0400 [thread overview]
Message-ID: <20260726195203.stable-0007@kernel.org> (raw)
In-Reply-To: <c5237e59-280e-4cf6-a77c-c71a61c75b5e@windriver.com>
> I see that the fix-up patch [1] has already been merged. Could you
> please double-check it?
Double-checked, and 6.12.y is complete: the original backport went out
in 6.12.97 and your fd-leak fixup in 6.12.98. In the merged result the
cross-superblock rejection sets err and jumps to mext_out, so the
fdput(donor) is no longer bypassed.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-26 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 14:38 [PATCH 6.12.y] ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT Yun Zhou
2026-07-24 15:26 ` Greg KH
2026-07-25 2:43 ` Zhou, Yun
2026-07-25 5:18 ` Greg KH
2026-07-26 12:04 ` Sasha Levin
2026-07-26 12:56 ` Zhou, Yun
2026-07-26 21:24 ` 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=20260726195203.stable-0007@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=patches@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=yun.zhou@windriver.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