From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: peterz@infradead.org
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, bp@suse.de, rientjes@google.com,
mhocko@suse.com, tglx@linutronix.de
Subject: Re: [PATCH] lockdep: Show address of "struct lockdep_map" at print_lock().
Date: Tue, 27 Mar 2018 05:58:49 +0900 [thread overview]
Message-ID: <201803270558.HCA41032.tVFJOFOMOFLHSQ@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20180326160549.GL4043@hirez.programming.kicks-ass.net>
Peter Zijlstra wrote:
> On Mon, Mar 26, 2018 at 07:18:33PM +0900, Tetsuo Handa wrote:
> > [ 628.863629] 2 locks held by a.out/1165:
> > [ 628.867533] #0: [ffffa3b438472e48] (&mm->mmap_sem){++++}, at: __do_page_fault+0x16f/0x4d0
> > [ 628.873570] #1: [ffffa3b4f2c52ac0] (&mapping->i_mmap_rwsem){++++}, at: rmap_walk_file+0x1d9/0x2a0
>
> Maybe change the string a little, because from the above it's not at all
> effident that the [] thing is the lock instance.
>
> > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> > index 12a2805..7835233 100644
> > --- a/kernel/locking/lockdep.c
> > +++ b/kernel/locking/lockdep.c
> > @@ -556,9 +556,9 @@ static void print_lock(struct held_lock *hlock)
> > return;
> > }
> >
> > + printk(KERN_CONT "[%px]", hlock->instance);
>
> And yeah, what Michal said, that wants to be %p, we're fine with the
> thing being hashed, all we want to do is equivalience, which can be done
> with hashed pinters too.
>
> > print_lock_name(lock_classes + class_idx - 1);
> > - printk(KERN_CONT ", at: [<%px>] %pS\n",
> > - (void *)hlock->acquire_ip, (void *)hlock->acquire_ip);
> > + printk(KERN_CONT ", at: %pS\n", (void *)hlock->acquire_ip);
> > }
>
> Otherwise no real objection to the patch.
>
I see. What about plain
- printk(KERN_CONT "[%px]", hlock->instance);
+ printk(KERN_CONT "%p", hlock->instance);
because we don't need to use [] ?
I'm trying to remove "[<%px>]" for hlock->acquire_ip field in order to
reduce amount of output, for debug_show_all_locks() prints a lot.
next prev parent reply other threads:[~2018-03-26 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 10:18 Tetsuo Handa
2018-03-26 13:19 ` Michal Hocko
2018-03-26 13:20 ` Michal Hocko
2018-03-26 16:05 ` Peter Zijlstra
2018-03-26 20:58 ` Tetsuo Handa [this message]
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
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=201803270558.HCA41032.tVFJOFOMOFLHSQ@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox