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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <002101d65012$6f861560$4e924020$@samsung.com>
Date:   Thu, 2 Jul 2020 10:45:16 +0900
From:   "Namjae Jeon" <namjae.jeon@...sung.com>
To:     "'Sasha Levin'" <sashal@...nel.org>
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,
Hi Sasha,
> 
> 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:
Okay, I'll do that next time!
Thank you!
> 
> [ Upstream commit 5267456e953fd8c5abd8e278b1cc6a9f9027ac0a ]
> 
> Thank you!
> 
> --
> Thanks,
> Sasha