From: Thorsten Leemhuis <regressions@leemhuis.info>
To: David Sterba <dsterba@suse.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Viktor Kuzmin <kvaster@gmail.com>
Subject: Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2
Date: Tue, 11 Oct 2022 14:09:50 +0200 [thread overview]
Message-ID: <8be1e839-2eb8-43d0-9ecb-6ff8c3aa3f2d@leemhuis.info> (raw)
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.
next reply other threads:[~2022-10-11 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 12:09 Thorsten Leemhuis [this message]
2022-10-14 11:07 ` Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2 David Sterba
2022-10-17 12:00 ` Thorsten Leemhuis
2022-10-20 13:11 ` David Sterba
2022-11-04 12:12 ` Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2 #forregzbot Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8be1e839-2eb8-43d0-9ecb-6ff8c3aa3f2d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kvaster@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).