From: "Chris Murphy" <lists@colorremedies.com>
To: "David Sterba" <dsterba@suse.cz>,
"Михаил Гаврилов" <mikhail.v.gavrilov@gmail.com>
Cc: "Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
Date: Tue, 26 Jul 2022 15:19:34 -0400 [thread overview]
Message-ID: <fa57195c-cd1e-464e-b099-7552f65e39f5@www.fastmail.com> (raw)
In-Reply-To: <20220726164250.GE13489@twin.jikos.cz>
On Tue, Jul 26, 2022, at 12:42 PM, David Sterba wrote:
> On Tue, Jul 26, 2022 at 05:32:54PM +0500, Mikhail Gavrilov wrote:
>> Hi guys.
>> Always with intensive writing on a btrfs volume, the message "BUG:
>> MAX_LOCKDEP_CHAIN_HLOCKS too low!" appears in the kernel logs.
>
> Increase the config value of LOCKDEP_CHAINS_BITS, default is 16, 18
> tends to work.
Fedora is using 17. I'll make a request to bump it to 18. Thanks.
--
Chris Murphy
next prev parent reply other threads:[~2022-07-26 19:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 12:32 BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! Mikhail Gavrilov
2022-07-26 16:42 ` David Sterba
2022-07-26 19:19 ` Chris Murphy [this message]
2022-07-26 19:21 ` Chris Murphy
2022-07-26 20:42 ` David Sterba
2022-08-03 19:28 ` Mikhail Gavrilov
2022-08-03 20:00 ` Chris Murphy
2022-08-04 7:35 ` Mikhail Gavrilov
2022-08-04 11:23 ` Tetsuo Handa
2023-01-24 20:27 ` Mikhail Gavrilov
2023-01-25 17:15 ` David Sterba
2023-01-26 9:47 ` Mikhail Gavrilov
2023-01-26 17:38 ` Boqun Feng
2023-01-26 18:30 ` Waiman Long
2023-01-26 18:59 ` Boqun Feng
2023-01-26 19:07 ` Waiman Long
2023-01-26 22:42 ` Mikhail Gavrilov
2023-01-26 22:51 ` Boqun Feng
2023-01-26 23:49 ` Boqun Feng
2023-01-27 0:20 ` Waiman Long
2023-01-27 3:37 ` Chris Murphy
2023-01-27 4:07 ` Boqun Feng
2023-01-27 5:35 ` Mikhail Gavrilov
2023-01-27 14:26 ` Waiman Long
2023-01-27 15:33 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2020-12-09 8:02 Dmitry Vyukov
2019-03-06 18:04 syzbot
2019-04-11 1:43 ` syzbot
2019-04-11 12:14 ` syzbot
2019-04-11 21:50 ` Benjamin Herrenschmidt
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=fa57195c-cd1e-464e-b099-7552f65e39f5@www.fastmail.com \
--to=lists@colorremedies.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
/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).