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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 12 May 2020 18:20:05 +0530
From:   Ritesh Harjani <>
To:     Greg KH <>
Cc:, "Theodore Y. Ts'o" <>,, Jan Kara <>,
        "Aneesh Kumar K . V" <>,
        Sasha Levin <>
Subject: Re: [PATCH] ext4: Don't set dioread_nolock by default for blocksize <

Hello Greg,

On 5/12/20 5:15 PM, Greg KH wrote:
> On Mon, May 11, 2020 at 01:37:59PM +0530, Ritesh Harjani wrote:
>> Hello stable-list,
>> I think this subjected patch [1] missed the below fixes tag.
>> I guess the subjected patch is only picked for 5.7. And
>> AFAIU, this patch will be needed for 5.6 as well.
>> Could you please do the needful.
>> Fixes: 244adf6426ee31a (ext4: make dioread_nolock the default)
>> [1]:
> This patch does not apply to the 5.6 kernel tree at all.  Please provide
> a working backport if you wish to see it present there.

Sorry if that's the case.
I tried both "git cherry-pick" and "git am" with patch mentioned @ [1]
to apply on branch "remotes/linux-stable/linux-5.6.y" of tree
and it applied cleanly.

Also, just noticed this patch in the queue. Is it that maybe you are
trying to apply it twice?

Do let me know if I am missing anything here.


Powered by blists - more mailing lists