From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org, stable@vger.kernel.org,
tejas.bharambe@outlook.com
Cc: Sasha Levin <sashal@kernel.org>,
patches@lists.linux.dev, linux-kernel@vger.kernel.org,
tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, Jianqiang kang <jianqkang@sina.cn>
Subject: Re: [PATCH 6.6.y] ext4: validate p_idx bounds in ext4_ext_correct_indexes
Date: Fri, 8 May 2026 17:11:44 -0400 [thread overview]
Message-ID: <de25b3e20974fadd-sashal@kernel.org> (raw)
In-Reply-To: <20260508065845.3031006-1-jianqkang@sina.cn>
> Subject: [PATCH 6.6.y] ext4: validate p_idx bounds in ext4_ext_correct_indexes
>
> commit 2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8 upstream.
Now queued for 6.6 and 6.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-05-08 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 6:58 [PATCH 6.6.y] ext4: validate p_idx bounds in ext4_ext_correct_indexes Jianqiang kang
2026-05-08 8:07 ` Andreas Dilger
2026-05-08 21:11 ` 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=de25b3e20974fadd-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jianqkang@sina.cn \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tejas.bharambe@outlook.com \
--cc=tytso@mit.edu \
/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