Messages in this thread | | | From | "chenjun (AM)" <> | Subject | Re: [PATCH 1/1] lockdep: pass curr_inner to print_lock_invalid_wait_context | Date | Mon, 20 Jun 2022 08:46:18 +0000 |
| |
在 2022/6/17 21:22, Peter Zijlstra 写道: > 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. > > >
Thanks for pointing this out.
-- Regards Chen Jun
| |