From: Luiz Capitulino <luizcap@amazon.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, <edward.lo@ambergroup.io>,
<almaz.alexandrovich@paragon-software.com>
Subject: Re: [6.1.y] Please apply 98bea253aa28ad8be2ce565a9ca21beb4a9419e5
Date: Tue, 6 Jun 2023 12:27:55 -0400 [thread overview]
Message-ID: <010e7cb2-f51f-c316-cd76-e457bcb257e4@amazon.com> (raw)
In-Reply-To: <2023060624-repave-audience-bfd5@gregkh>
On 2023-06-06 12:22, Greg KH wrote:
>
>
>
> On Tue, Jun 06, 2023 at 10:56:34AM -0400, Luiz Capitulino wrote:
>>
>>
>> On 2023-06-01 17:17, Luiz Capitulino wrote:
>>>
>>> It fixes CVE-2022-48425 and is applied to 5.15.y and 6.3.y. I quickly tested
>>> the commit by mounting an NTFS partition and building a kernel in it.
>>
>> Humble ping?
>
> 5 days later? Please give us a chance to catch up...
Sorry Greg, I know you're all very busy. I saw you replying to other requests
and thought you might have missed this one.
>
>>> """
>>> commit 98bea253aa28ad8be2ce565a9ca21beb4a9419e5
>>> Author: Edward Lo <edward.lo@ambergroup.io>
>>> Date: Sat Nov 5 23:39:44 2022 +0800
>>>
>>> fs/ntfs3: Validate MFT flags before replaying logs
>
> And really, ntfs? For an issue that was fixed last year? What's the
> rush? :)
No rush, I just thought this one was missed.
Thanks for replying and sorry again for the nudge.
- Luiz
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-06-06 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 21:17 [6.1.y] Please apply 98bea253aa28ad8be2ce565a9ca21beb4a9419e5 Luiz Capitulino
2023-06-06 14:56 ` Luiz Capitulino
2023-06-06 16:22 ` Greg KH
2023-06-06 16:27 ` Luiz Capitulino [this message]
2023-06-07 12:47 ` Greg KH
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=010e7cb2-f51f-c316-cd76-e457bcb257e4@amazon.com \
--to=luizcap@amazon.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=edward.lo@ambergroup.io \
--cc=gregkh@linuxfoundation.org \
--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.