From: Greg KH <gregkh@linuxfoundation.org>
To: bin.lan.cn@windriver.com
Cc: stable@vger.kernel.org, rtm@csail.mit.edu,
almaz.alexandrovich@paragon-software.com
Subject: Re: [PATCH 5.15.y] fs/ntfs3: Fixed overflow check in mi_enum_attr()
Date: Tue, 22 Apr 2025 15:30:24 +0200 [thread overview]
Message-ID: <2025042214-flight-reckless-63d1@gregkh> (raw)
In-Reply-To: <20250328091824.1646736-1-bin.lan.cn@windriver.com>
On Fri, Mar 28, 2025 at 05:18:24PM +0800, bin.lan.cn@windriver.com wrote:
> From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
>
> [ Upstream commit 652cfeb43d6b9aba5c7c4902bed7a7340df131fb ]
>
> Reported-by: Robert Morris <rtm@csail.mit.edu>
> Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
> Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
> Signed-off-by: He Zhe <zhe.he@windriver.com>
> ---
> Build test passed.
> ---
You didn't document what you changed from the original :(
prev parent reply other threads:[~2025-04-22 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 9:18 [PATCH 5.15.y] fs/ntfs3: Fixed overflow check in mi_enum_attr() bin.lan.cn
2025-03-28 17:03 ` Sasha Levin
2025-04-22 13:30 ` Greg KH [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=2025042214-flight-reckless-63d1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=bin.lan.cn@windriver.com \
--cc=rtm@csail.mit.edu \
--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