From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: jianqi.ren.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] fs/ntfs3: Fixed overflow check in mi_enum_attr()
Date: Mon, 9 Dec 2024 09:35:04 -0500 [thread overview]
Message-ID: <20241209081750-0d5e8a9d122a3494@stable.kernel.org> (raw)
In-Reply-To: <20241209065223.3427374-1-jianqi.ren.cn@windriver.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 652cfeb43d6b9aba5c7c4902bed7a7340df131fb
WARNING: Author mismatch between patch and upstream commit:
Backport author: <jianqi.ren.cn@windriver.com>
Commit author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 8c77398c7261)
6.1.y | Present (different SHA1: be684526fad4)
Note: The patch differs from the upstream commit:
---
1: 652cfeb43d6b9 ! 1: 77aacf84111d3 fs/ntfs3: Fixed overflow check in mi_enum_attr()
@@ Metadata
## Commit message ##
fs/ntfs3: Fixed overflow check in mi_enum_attr()
+ [ Upstream commit 652cfeb43d6b9aba5c7c4902bed7a7340df131fb ]
+
Reported-by: Robert Morris <rtm@csail.mit.edu>
Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
+ Signed-off-by: Sasha Levin <sashal@kernel.org>
+ Signed-off-by: Jianqi.ren.cn@windriver.com <jianqi.ren.cn@windriver.com>
## fs/ntfs3/record.c ##
@@ fs/ntfs3/record.c: struct ATTRIB *mi_enum_attr(struct mft_inode *mi, struct ATTRIB *attr)
@@ fs/ntfs3/record.c: struct ATTRIB *mi_enum_attr(struct mft_inode *mi, struct ATTR
+ if (le32_to_cpu(attr->res.data_size) > asize - t16)
return NULL;
- t32 = sizeof(short) * attr->name_len;
+ if (attr->name_len &&
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2024-12-09 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 6:52 [PATCH 6.1.y] fs/ntfs3: Fixed overflow check in mi_enum_attr() jianqi.ren.cn
2024-12-09 6:22 ` Greg KH
2024-12-09 14:35 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 10:08 jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin
2024-12-09 8:05 jianqi.ren.cn
2024-12-09 14:35 ` Sasha Levin
2024-12-04 3:29 jianqi.ren.cn
2024-12-04 2:44 ` Sasha Levin
2024-12-11 8:16 ` Greg KH
2024-11-30 15:58 Nikita Zhandarovich
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=20241209081750-0d5e8a9d122a3494@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jianqi.ren.cn@windriver.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 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.