From: Boqun Feng <boqun.feng@gmail.com>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] lockdep: suggest the fix for "lockdep bfs error:-1" on print_bfs_bug
Date: Mon, 5 Aug 2024 10:43:08 -0700 [thread overview]
Message-ID: <ZrEPLFDGSSS3Dh80@tardis> (raw)
In-Reply-To: <Zqkmy0lS-9Sw0M9j@uudg.org>
On Tue, Jul 30, 2024 at 02:45:47PM -0300, Luis Claudio R. Goncalves wrote:
> When lockdep fails while performing the Breadth-first-search operation
> due to lack of memory, hint that increasing the value of the config
> switch LOCKDEP_CIRCULAR_QUEUE_BITS should fix the warning.
>
> Preface the scary backtrace with the suggestion:
>
> [ 163.849242] Increase LOCKDEP_CIRCULAR_QUEUE_BITS to avoid this warning:
> [ 163.849248] ------------[ cut here ]------------
> [ 163.849250] lockdep bfs error:-1
> [ 163.849263] WARNING: CPU: 24 PID: 2454 at kernel/locking/lockdep.c:2091 print_bfs_bug+0x27/0x40
> ...
>
> Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
> Reviewed-by: Waiman Long <longman@redhat.com>
> Signed-off-by: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
Queued at:
https://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git/
lockdep-for-tip
Thanks!
Regards,
Boqun
> ---
>
> Changes in v2:
> - removed extra space from the if condition.
>
> kernel/locking/lockdep.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> index 58c88220a478a..1cf6d9fdddc9c 100644
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -2067,6 +2067,9 @@ static noinline void print_bfs_bug(int ret)
> /*
> * Breadth-first-search failed, graph got corrupted?
> */
> + if (ret == BFS_EQUEUEFULL)
> + pr_warn("Increase LOCKDEP_CIRCULAR_QUEUE_BITS to avoid this warning:\n");
> +
> WARN(1, "lockdep bfs error:%d\n", ret);
> }
>
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-08-05 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 17:45 [PATCH V2] lockdep: suggest the fix for "lockdep bfs error:-1" on print_bfs_bug Luis Claudio R. Goncalves
2024-08-02 15:10 ` Peter Zijlstra
2024-08-05 17:43 ` Boqun Feng [this message]
2024-08-06 10:51 ` [tip: locking/core] " tip-bot2 for Luis Claudio R. Goncalves
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=ZrEPLFDGSSS3Dh80@tardis \
--to=boqun.feng@gmail.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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