linux-kernel - Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2

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

Message-ID: <8be1e839-2eb8-43d0-9ecb-6ff8c3aa3f2d@leemhuis.info>
Date:   Tue, 11 Oct 2022 14:09:50 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     David Sterba <dsterba@...e.com>
Cc:     Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
        linux-btrfs <linux-btrfs@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        Viktor Kuzmin <kvaster@...il.com>
Subject: Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2

Hi, this is your Linux kernel regression tracker speaking.

David, I noticed a regression report in bugzilla.kernel.org apparently
caused by a changed of yours. As many (most?) kernel developer don't
keep an eye on the bug-tracker, I decided to forward the report by mail.
Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216559 :

> [reply] [−] Description Viktor Kuzmin 2022-10-08 20:41:32 UTC
> 
> In linux 6.0.0 there was change in block-group.c file in function btrfs_rmap_block:
> [...]

FWIW, the reporter (CCed) here meant change ac0677348f3c2 ("btrfs: merge
calculations for simple striped profiles in btrfs_rmap_block").
Reverting it fixes the problem.

> After this change I have a crash with DIVIDE by ZERO error. It seems that map->sub_stripes can be zero.
> 
> My setup is 2x 1TB nvme with space_cache=v2 and discard=async btrfs raid0.

See the ticket for more details and screenshots from the crash.

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: ac0677348f3c2
https://bugzilla.kernel.org/show_bug.cgi?id=216559
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.