From: Peter Zijlstra <peterz@infradead.org>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>, David Sterba <dsterba@suse.cz>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>
Subject: Re: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
Date: Mon, 10 Mar 2025 12:23:15 +0100 [thread overview]
Message-ID: <20250310112315.GS16878@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CABXGCsOz43OKLXUcJcqHfNpyppgK6EbfZ7aoXYPS1t21+N6i8g@mail.gmail.com>
On Mon, Mar 10, 2025 at 03:51:21AM +0500, Mikhail Gavrilov wrote:
> On Fri, Jan 27, 2023 at 8:33 PM Chris Murphy <lists@colorremedies.com> wrote:
> > Also, at least in Fedora Rawhide where the mainline debug kernels appear, mostly get used non-interactively with automated tests. So if we're going to discover lockdep issues, we need the kernel logs to be reliable at the time those tests are run, and we don't have a practical way of adding another boot parameter just for these tests.
> >
> > Anyway I went ahead and submitted an MR to bump this to 19.
> > https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2271
> >
>
> Hi,
> Two years have passed since my last message in this thread.
> And now CONFIG_LOCKDEP_CHAIN_BITS=19 has become insufficient.
> https://gitlab.com/cki-project/kernel-ark/-/blob/os-build/redhat/configs/fedora/generic/CONFIG_LOCKDEP_CHAINS_BITS
>
> I am again faced by "BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!"
> Still not exists a boot parameter that could redefine
> MAX_LOCKDEP_CHAIN_HLOCKS at boot time?
> And what should we do? Again, bump CONFIG_LOCKDEP_CHAIN_BITS? Now up to 20?
What are you actually doing? Anyway, check your chains to see if there's
anything obviously silly causing a combinatorial explosion.
next prev parent reply other threads:[~2025-03-10 11:23 UTC|newest]
Thread overview: 37+ 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
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
2025-03-09 22:51 ` Mikhail Gavrilov
2025-03-10 11:23 ` Peter Zijlstra [this message]
2025-03-10 9:08 ` Peter Zijlstra
2025-03-10 13:01 ` Peter Zijlstra
2025-03-10 11:21 ` Peter Zijlstra
2025-03-10 16:37 ` Boqun Feng
2025-09-23 7:03 ` Mikhail Gavrilov
-- 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=20250310112315.GS16878@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=dsterba@suse.cz \
--cc=joel@joelfernandes.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=longman@redhat.com \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=mingo@redhat.com \
--cc=will@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