Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   "chenjun (AM)" <chenjun102@huawei.com>
To:     Peter Zijlstra <peterz@infradead.org>
CC:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "mingo@redhat.com" <mingo@redhat.com>,
        "will@kernel.org" <will@kernel.org>,
        "xuqiang (M)" <xuqiang36@huawei.com>
Subject: Re: [PATCH 1/1] lockdep: pass curr_inner to
 print_lock_invalid_wait_context
Thread-Topic: [PATCH 1/1] lockdep: pass curr_inner to
 print_lock_invalid_wait_context
Thread-Index: AQHYgk0/9VHjoiftGU6cvzdp/UjhBQ==
Date:   Mon, 20 Jun 2022 08:46:18 +0000
Message-ID: <233a8820e3df4c8ca594c4a78fdb0fb9@huawei.com>
References: <20220616134042.130002-1-chenjun102@huawei.com>
 <YqyAAvSw3+0GyHhg@worktop.programming.kicks-ass.net>
Accept-Language: zh-CN, en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Precedence: bulk

在 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