linux-ext4 - Re: bug with large

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 28 Jul 2021 19:07:33 +0300
From:   Благодаренко Артём 
        <artem.blagodarenko@...il.com>
To:     Andreas Dilger <adilger@...ger.ca>
Cc:     Carlos Carvalho <carlos@...ica.ufpr.br>, linux-ext4@...r.kernel.org
Subject: Re: bug with large_dir in 5.12.17

Hello Andreas,

This issue is reproducible in case the “large_dir” option is set initially. The partition is fresh, created just before the test started.

1560000 names created
ln: failed to create hard link 'n0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001571063': File exists
ln: failed to access 'n0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001571384': Structure needs cleaning
ln: failed to access 'n0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001572335': Structure needs cleaning
ln: failed to access 'n0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001573095': Structure needs cleaning
ln: failed to access 'n0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001574809': Structure needs cleaning
ln: failed to access 'n0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001576070': Structure needs cleaning

Best regards,
Artem Blagodarenko


> On 27 Jul 2021, at 09:22, Andreas Dilger <adilger@...ger.ca> wrote:
> 
> On Jul 22, 2021, at 8:23 AM, Carlos Carvalho <carlos@...ica.ufpr.br> 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.
> 
> Hi Carlos,
> are you able to reproduce this error on a new directory that did not hit
> the 2-level htree limit before enabling large_dir, or did you only see this
> with directories that hit the 2-level htree limit before the update?
> Did you test on any newer kernels than 5.2.17?
> 
> Cheers, Andreas
> 
> 
> 
> 
>