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:   Mon, 11 May 2020 13:37:59 +0530
From:   Ritesh Harjani <>
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 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)



On 3/29/20 7:47 AM, Theodore Y. Ts'o wrote:
> On Sat, Mar 28, 2020 at 01:37:44AM +0530, Ritesh Harjani wrote:
>> Currently on calling echo 3 > drop_caches on host machine, we see
>> FS corruption in the guest. This happens on Power machine where
>> blocksize < pagesize.
>> So as a temporary workaound don't enable dioread_nolock by default
>> for blocksize < pagesize until we identify the root cause.
>> Also emit a warning msg in case if this mount option is manually
>> enabled for blocksize < pagesize.
>> Reported-by: Aneesh Kumar K.V <>
>> Signed-off-by: Ritesh Harjani <>
> Thanks, applied.
> 					- Ted

Powered by blists - more mailing lists