From: Nikolay Borisov <nborisov@suse.com>
To: dsterba@suse.cz, Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Subject: Re: 5.14-0-rc5, splat in block_group_cache_tree_search while __btrfs_unlink_inode
Date: Mon, 16 Aug 2021 13:27:35 +0300 [thread overview]
Message-ID: <1e15b3ab-e3a3-548b-86a7-c309deed0f12@suse.com> (raw)
In-Reply-To: <20210816102022.GU5047@twin.jikos.cz>
On 16.08.21 г. 13:20, David Sterba wrote:
> On Fri, Aug 13, 2021 at 10:33:05PM -0600, Chris Murphy wrote:
>> I get the following call trace about 0.6s after dnf completes an
>> update which I imagine deletes many files. I'll try to reproduce and
>> get /proc/lock_stat
>>
>> [ 95.674507] kernel: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
>
> The message "BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low" is related to
> lockdep and not a btrfs problem, but it appears from time to time and as
> Johannes said either increase the config variable, or ignore it.
>
But is not a bug if code triggers it? I.e I think it's a signal of
misbehaving code. CC'ed PeterZ who can hopefully shed some light on this.
next prev parent reply other threads:[~2021-08-16 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 4:33 5.14-0-rc5, splat in block_group_cache_tree_search while __btrfs_unlink_inode Chris Murphy
2021-08-16 7:17 ` Johannes Thumshirn
2021-08-17 3:21 ` Chris Murphy
2021-08-16 10:20 ` David Sterba
2021-08-16 10:27 ` Nikolay Borisov [this message]
2021-08-16 10:52 ` David Sterba
2021-08-16 15:11 ` Peter Zijlstra
2021-08-16 15:40 ` Matthew Wilcox
2021-08-16 20:43 ` David Sterba
2021-08-17 8:46 ` Peter Zijlstra
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=1e15b3ab-e3a3-548b-86a7-c309deed0f12@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=peterz@infradead.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