From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Borislav Petkov <bp@suse.de>,
David Rientjes <rientjes@google.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] lockdep: Show address of "struct lockdep_map" at print_lock().
Date: Mon, 26 Mar 2018 15:19:11 +0200 [thread overview]
Message-ID: <20180326131911.GI5652@dhcp22.suse.cz> (raw)
In-Reply-To: <1522059513-5461-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp>
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
next prev parent reply other threads:[~2018-03-26 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 10:18 [PATCH] lockdep: Show address of "struct lockdep_map" at print_lock() Tetsuo Handa
2018-03-26 13:19 ` Michal Hocko [this message]
2018-03-26 13:20 ` Michal Hocko
2018-03-26 16:05 ` Peter Zijlstra
2018-03-26 20:58 ` Tetsuo Handa
2018-03-27 10:41 ` [PATCH v2] " Tetsuo Handa
2018-03-27 10:50 ` Michal Hocko
2018-03-27 20:23 ` David Rientjes
2018-03-29 10:26 ` Tetsuo Handa
2018-03-29 12:01 ` Peter Zijlstra
2018-03-29 12:45 ` [tip:locking/core] lockdep: Make the lock debug output more useful tip-bot for Tetsuo Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180326131911.GI5652@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.