From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Miguel García" <miguelgarciaroman8@gmail.com>,
"Sasha Levin" <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] fs/ntfs3: Fix shift-out-of-bounds in ntfs_fill_super
Date: Thu, 13 Mar 2025 05:08:48 -0400 [thread overview]
Message-ID: <20250312221634-814bd966ecd9cc70@stable.kernel.org> (raw)
In-Reply-To: <20250310084820.20680-1-miguelgarciaroman8@gmail.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 91a4b1ee78cb100b19b70f077c247f211110348f
WARNING: Author mismatch between patch and upstream commit:
Backport author: =?UTF-8?q?Miguel=20Garc=C3=ADa?=<miguelgarciaroman8@gmail.com>
Commit author: Konstantin Komarov<almaz.alexandrovich@paragon-software.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 91a4b1ee78cb1 < -: ------------- fs/ntfs3: Fix shift-out-of-bounds in ntfs_fill_super
-: ------------- > 1: eda5808d02243 fs/ntfs3: Fix shift-out-of-bounds in ntfs_fill_super
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-03-13 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 14:56 [PATCH 5.15.y] fs/ntfs3: Fix shift-out-of-bounds in ntfs_fill_super Miguel García
2025-03-10 2:14 ` Sasha Levin
2025-03-10 8:48 ` Miguel García
2025-03-10 16:20 ` Greg KH
2025-03-13 9:08 ` Sasha Levin [this message]
2025-03-10 16:21 ` Greg KH
2025-03-10 17:19 ` [PATCH 6.1.y] " Miguel García
2025-03-13 9:11 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2025-03-09 14:54 [PATCH 5.15.y] " Miguel García
2025-03-10 2:14 ` Sasha Levin
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=20250312221634-814bd966ecd9cc70@stable.kernel.org \
--to=sashal@kernel.org \
--cc=miguelgarciaroman8@gmail.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