[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YqyAAvSw3+0GyHhg@worktop.programming.kicks-ass.net>
Date: Fri, 17 Jun 2022 15:22:10 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Chen Jun <chenjun102@...wei.com>
Cc: linux-kernel@...r.kernel.org, mingo@...hat.com, will@...nel.org,
xuqiang36@...wei.com
Subject: Re: [PATCH 1/1] lockdep: pass curr_inner to
print_lock_invalid_wait_context
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.
Powered by blists - more mailing lists