From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751897AbeCZNTU (ORCPT ); Mon, 26 Mar 2018 09:19:20 -0400 Received: from mx2.suse.de ([195.135.220.15]:59054 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751132AbeCZNTQ (ORCPT ); Mon, 26 Mar 2018 09:19:16 -0400 Date: Mon, 26 Mar 2018 15:19:11 +0200 From: Michal Hocko To: Tetsuo Handa Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Borislav Petkov , David Rientjes , Thomas Gleixner Subject: Re: [PATCH] lockdep: Show address of "struct lockdep_map" at print_lock(). Message-ID: <20180326131911.GI5652@dhcp22.suse.cz> References: <1522059513-5461-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1522059513-5461-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 26-03-18 19:18:33, Tetsuo Handa wrote: > Currently, print_lock() is printing hlock->acquire_ip field in both > "[<%px>]" and "%pS" format. But "[<%px>]" is little useful nowadays, for > we use scripts/faddr2line which receives "%pS" for finding the location > in the source code. > > Since "struct lockdep_map" is embedded into lock objects, we can know > which instance of a lock object is acquired using hlock->instance field. > This will help finding which threads are causing a lock contention when > e.g. the OOM reaper failed to acquire an OOM victim's mmap_sem for read. How? All I can see is that we can match which instances are the same. This would be an interesting thing to know AFAICS because you can tell different instances of lock apart. So the patch makes some sense to me, I am just not sure about changelog. -- Michal Hocko SUSE Labs