mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lockdep: suggest the fix for "lockdep bfs error:-1" on print_bfs_bug
Date: Mon, 29 Jul 2024 13:22:25 -0400	[thread overview]
Message-ID: <706a4fd7-e0b0-4ada-b269-04978b0a5265@redhat.com> (raw)
In-Reply-To: <ZqfJDTn9rCQ1eVnz@uudg.org>


On 7/29/24 12:53, Luis Claudio R. Goncalves wrote:
> On Fri, Jul 26, 2024 at 02:24:28PM -0700, Boqun Feng wrote:
>> On Thu, Jul 25, 2024 at 03:45:57PM -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 configuration
>>> switch LOCKDEP_CIRCULAR_QUEUE_BITS should fix the warning.
>>>
>>> Preface the scary bactrace 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
>>>      ...
>>>
>>> Signed-off-by: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
>>> ---
>>>   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)
>> This line has an extra space after "ret", but otherwise it looks fine.
> Should I send a v2 of the patch with the extra whitespace removed?
>
> Luis

Yes, you should. Other than the extra space, the patch looks good to me too.

Reviewed-by: Waiman Long <longman@redhat.com>

You can also add our review-by tags in your v2 patch.

Cheers,
Longman

>
>> Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
>>
>> Regards,
>> Boqun
>>
>>> +		pr_warn("Increase LOCKDEP_CIRCULAR_QUEUE_BITS to avoid this warning:\n");
>>> +
>>>   	WARN(1, "lockdep bfs error:%d\n", ret);
>>>   }
>>>   
>>> -- 
>>> 2.45.2
>>>
> ---end quoted text---
>


      reply	other threads:[~2024-07-29 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 18:45 Luis Claudio R. Goncalves
2024-07-26 21:24 ` Boqun Feng
2024-07-29 16:53   ` Luis Claudio R. Goncalves
2024-07-29 17:22     ` Waiman Long [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=706a4fd7-e0b0-4ada-b269-04978b0a5265@redhat.com \
    --to=longman@redhat.com \
    --cc=boqun.feng@gmail.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®