From: Peter Zijlstra <peterz@infradead.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Andreas Messerschmid <andreas@linutronix.de>
Subject: Re: [PATCH] lockdep: make print_lock_name() robust against non-existing lock_class
Date: Thu, 16 Apr 2015 17:35:03 +0200 [thread overview]
Message-ID: <20150416153503.GC12676@worktop.ger.corp.intel.com> (raw)
In-Reply-To: <552FCC2D.4050304@linutronix.de>
On Thu, Apr 16, 2015 at 04:50:21PM +0200, Sebastian Andrzej Siewior wrote:
> Andreas confirmed that it works for him on v3.18 with minor adjustment.
>
> <---
> + struct held_lock lock = READ_ONCE(*hlock);
> + unsigned int class_idx = lock.class_idx;
> --->
>
I'm confused by the need for that. What was the failure with the
proposed patch?
next prev parent reply other threads:[~2015-04-16 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 13:24 [PATCH] lockdep: make print_lock_name() robust against non-existing lock_class Sebastian Andrzej Siewior
2015-04-15 14:14 ` Peter Zijlstra
2015-04-16 14:50 ` Sebastian Andrzej Siewior
2015-04-16 15:35 ` Peter Zijlstra [this message]
2015-04-16 15:39 ` Sebastian Andrzej Siewior
2015-04-16 15:50 ` 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=20150416153503.GC12676@worktop.ger.corp.intel.com \
--to=peterz@infradead.org \
--cc=andreas@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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.