From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: KASAN splat during mount on 5.4.5, no reproducer
Date: Mon, 3 Feb 2020 13:44:25 -0500 [thread overview]
Message-ID: <20200203184425.GV13306@hungrycats.org> (raw)
In-Reply-To: <20200120194650.GO3929@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On Mon, Jan 20, 2020 at 08:46:50PM +0100, David Sterba wrote:
> On Sat, Dec 28, 2019 at 03:03:26PM -0500, Zygo Blaxell wrote:
> >
> > [...etc...it dumps the same stacks again in the BUG]
> >
> > The deepest level of fs/btrfs code is the list_del_init in
> > clean_dirty_subvols.
> >
> > After a reboot the next mount (and all subsequent mounts so far)
> > was successful. I don't have a reproducer.
>
> For the record, this and other KASAN reports regarding reloc root, is
> going to be fixed in 5.4.14, "btrfs: relocation: fix reloc_root lifespan
> and access" (6282675e6708ec78). Thanks for the reports and debugging
> help.
Confirmed: I have not seen this bug since applying the first versions of
the patch to my test kernels in 5.4.8. I've been testing continuously
since then, replacing the early version with the final upstream version
in 5.4.14, and now running 5.4.16. After applying "Btrfs: fix race
between adding and putting tree mod seq elements and nodes" I have seen
no crashing bugs _at all_ (no deadlock, BUG_ON or KASAN).
Thank you for all the fixes! Much appreciated!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-02-03 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 20:03 KASAN splat during mount on 5.4.5, no reproducer Zygo Blaxell
2019-12-29 1:32 ` Qu Wenruo
2019-12-29 5:14 ` Zygo Blaxell
2020-01-20 19:46 ` David Sterba
2020-02-03 18:44 ` Zygo Blaxell [this message]
2020-02-13 5:20 ` KASAN splat during mount on 5.4.5...and 5.5.3 Zygo Blaxell
2020-02-13 5:57 ` Qu Wenruo
2020-02-13 18:36 ` Zygo Blaxell
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=20200203184425.GV13306@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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