From: Chris Webb <chris@arachsys.com>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: BUG_ON in fs/bcachefs/btree_iter.c
Date: Sat, 9 Oct 2021 10:20:23 +0100 [thread overview]
Message-ID: <20211009092022.GA21732@arachsys.com> (raw)
In-Reply-To: <20211007115230.GA24322@arachsys.com>
Hi Kent. A quick follow-up to the bug report I sent to the list on Thursday:
Chris Webb <chris@arachsys.com> writes:
> However, when I test a simple replicated config on two small zram disks,
[...]
> I can get instantly get a reliable BUG_ON at fs/bcachefs/btree_iter.c:2475
> by running a data rereplicate, which should presumably be a no-op?
[...]
> [ 238.033452] kernel BUG at fs/bcachefs/btree_iter.c:2475!
[...]
> [ 273.286870] kernel BUG at fs/bcachefs/btree_iter.c:367!
I can no longer trigger either of these bugs following your recent set of
patches from 2021-10-07: 222a80c6 to c988c58e.
Thanks, and sorry I forgot to copy you on both the original report and the
btrfs-tools libsodium scrypt patch which I sent to the linux-bcachefs
mailing list. (I was so excited at finding a project mailing list, I forgot
to actually CC: the maintainer!)
Best wishes,
Chris.
prev parent reply other threads:[~2021-10-09 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 11:52 BUG_ON in fs/bcachefs/btree_iter.c Chris Webb
2021-10-09 9:20 ` Chris Webb [this message]
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=20211009092022.GA21732@arachsys.com \
--to=chris@arachsys.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcachefs@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