linux-kernel - Re: [BUG] btrfs potential failure on 32 core LTP test (fallocate05)

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, 30 Jun 2021 10:34:56 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To:     Josef Bacik <josef@...icpanda.com>, Chris Mason <clm@...com>,
        David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "kernel-team@...ts.ubuntu.com" <kernel-team@...ts.ubuntu.com>,
        "ltp@...ts.linux.it" <ltp@...ts.linux.it>,
        Qu Wenruo <wqu@...e.com>, Filipe Manana <fdmanana@...e.com>
Subject: Re: [BUG] btrfs potential failure on 32 core LTP test (fallocate05)

On 29/06/2021 20:32, Josef Bacik wrote:
> On 6/29/21 2:28 PM, Krzysztof Kozlowski wrote:
>> On 29/06/2021 20:06, Krzysztof Kozlowski wrote:
>>> Minor update - it's not only Azure's. AWS m5.8xlarge and m5.16xlarge (32
>>> and 64 cores) fail similarly. I'll try later also QEMU machines with
>>> different amount of CPUs.
>>>
>>
>> Test on QEMU machine with 31 CPUs passes. With 32 CPUs - failure as
>> reported.
>>
>> dmesg is empty - no error around this.
>>
>> Maybe something with per-cpu variables?
> 
> Ah yeah, so since you are further into this than I am, want to give my recent 
> batch of fixes a try?
> 
> https://github.com/josefbacik/linux/tree/delalloc-shrink
> 
> This might actually resolve the problems.  If not I'm getting one of our 64cpu 
> boxes setup to test this, I also couldn't reproduce it on my smaller local 
> machines.  Thanks,

I just gave ita try on v5.13 + merge of your branch and it fixes the
issue, at least on QEMU with 32 and 64 CPUs.

Would be good to find the exact commit fixing it to be sure it gets
backported to stables.


Best regards,
Krzysztof