linux-kernel - Re: [PATCH 5.7.y 0/5] exfat stable patches for 5.7.y

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 1 Jul 2020 21:38:24 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     Namjae Jeon <namjae.jeon@...sung.com>
Cc:     gregkh@...uxfoundation.org, stable@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5.7.y 0/5] exfat stable patches for 5.7.y

Hi Namjae,

On Thu, Jul 02, 2020 at 08:20:19AM +0900, Namjae Jeon wrote:
>Could you please push exfat stable patches into 5.7.y kernel tree ?

I've queued them up, however it would be much easier if for commits that
don't require any modification to allow backporting you would just
provide the commit ids in Linus's tree rather than the patches
themselves.

I do see that you had to modify this one:

>Sungjong Seo (1):
>  exfat: flush dirty metadata in fsync

In which case, a header in the commit message indicating the upstream
commit id would be appriciated. Something like this:

[ Upstream commit 5267456e953fd8c5abd8e278b1cc6a9f9027ac0a ]

Thank you!

-- 
Thanks,
Sasha