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:   Thu, 29 Jul 2021 22:23:35 +0300
From:   Благодаренко Артём 
To:     Carlos Carvalho <>
Cc:, Theodore Tso <>,
        Andreas Dilger <>
Subject: Re: bug with large_dir in 5.12.17


It looks like the fix b5776e7524afbd4569978ff790864755c438bba7 "ext4: fix potential htree index checksum corruption” introduced this regression.
I reverted it and my test from previous message passed the dangerous level of 1570000 names count.
Now test is still in progress. 2520000 names are already created.

I am searching the way to fix this.

Best regards,
Artem Blagodarenko.

> On 22 Jul 2021, at 17:23, Carlos Carvalho <> wrote:
> There is a bug when enabling large_dir in 5.12.17. I got this during a backup:
> index full, reach max htree level :2
> Large directory feature is not enabled on this filesystem
> So I unmounted, ran tune2fs -O large_dir /dev/device and mounted again. However
> this error appeared:
> dx_probe:864: inode #576594294: block 144245: comm rsync: directory leaf block found instead of index block
> I unmounted, ran fsck and it "salvaged" a bunch of directories. However at the
> next backup run the same errors appeared again.
> This is with vanilla 5.2.17.

Powered by blists - more mailing lists