linux-kernel - Re: [PATCH 1/1] lockdep: pass curr_inner to print_lock_invalid_wait

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <233a8820e3df4c8ca594c4a78fdb0fb9@huawei.com>
Date:   Mon, 20 Jun 2022 08:46:18 +0000
From:   "chenjun (AM)" <chenjun102@...wei.com>
To:     Peter Zijlstra <peterz@...radead.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "will@...nel.org" <will@...nel.org>,
        "xuqiang (M)" <xuqiang36@...wei.com>
Subject: Re: [PATCH 1/1] lockdep: pass curr_inner to
 print_lock_invalid_wait_context

在 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