From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
Alexey Panov <apanov@astralinux.ru>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
ntfs3@lists.linux.dev, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, Edward Lo <loyuantsung@gmail.com>
Subject: Re: [PATCH 5.15/6.1] fs/ntfs3: Return error for inconsistent extended attributes
Date: Wed, 10 Jun 2026 20:45:18 -0400 [thread overview]
Message-ID: <20260610-stable-reply-0002@kernel.org> (raw)
In-Reply-To: <20260610085204.21142-1-apanov@astralinux.ru>
On Tue, Jun 10, 2026 at 11:52:04AM +0300, Alexey Panov wrote:
> [PATCH 5.15/6.1] fs/ntfs3: Return error for inconsistent extended attributes
> Backport fix for CVE-2023-54125
Queued for 6.1 and 5.15, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-11 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:52 [PATCH 5.15/6.1] fs/ntfs3: Return error for inconsistent extended attributes Alexey Panov
2026-06-11 0:45 ` 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=20260610-stable-reply-0002@kernel.org \
--to=sashal@kernel.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=apanov@astralinux.ru \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loyuantsung@gmail.com \
--cc=lvc-project@linuxtesting.org \
--cc=ntfs3@lists.linux.dev \
--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 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.