linux-kernel - Re: 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221014110708.GE13389@suse.cz>
Date:   Fri, 14 Oct 2022 13:07:08 +0200
From:   David Sterba <dsterba@...e.cz>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     David Sterba <dsterba@...e.com>, 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: Re: Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2

On Tue, Oct 11, 2022 at 02:09:50PM +0200, Thorsten Leemhuis wrote:
> 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 :

Thanks, you don't need to forward the mails as I'm on CC of all bugzilla
updates where the btrfs virtual assignee is also present. But feel free
to ping regarding any regressions you're tracking and would like an
update.

Inspired by the LPC talk about bugzilla I went through all 650+ btrfs
bugs and closed what looked either fixed or not relevant anymore. The
rest are recent reports or bugs that may need to be moved elsewhere.
As kernel.org bugzilla is recommended for reports in our community
documentation I monitor new bugs but with variable reaction time.