From: Peter Zijlstra <peterz@infradead.org>
To: Chen Jun <chenjun102@huawei.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, will@kernel.org,
xuqiang36@huawei.com
Subject: Re: [PATCH 1/1] lockdep: pass curr_inner to print_lock_invalid_wait_context
Date: Fri, 17 Jun 2022 15:22:10 +0200 [thread overview]
Message-ID: <YqyAAvSw3+0GyHhg@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220616134042.130002-1-chenjun102@huawei.com>
On Thu, Jun 16, 2022 at 01:40:42PM +0000, Chen Jun wrote:
> Same information (task_wait_context(curr)) is printed twice.
Yes, because at that point the inner and outer context are the same.
> curr_inner in check_wait_context is what we need.
IIRC it simply prints the task_wait_context as a starting point, the
lockdep_print_held_locks() should include the contexts for each of
those, after which you can compute the resulting value.
IOW, the information is complete.
next prev parent reply other threads:[~2022-06-17 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 13:40 Chen Jun
2022-06-17 13:22 ` Peter Zijlstra [this message]
2022-06-20 8:46 ` chenjun (AM)
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=YqyAAvSw3+0GyHhg@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chenjun102@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=will@kernel.org \
--cc=xuqiang36@huawei.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
Powered by JetHome