From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Florian Mickler <florian@mickler.org>
Cc: Andrea Righi <andrea@betterlinux.com>,
Len Brown <lenb@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: fix acpi_power_off lockdep splat
Date: Sun, 3 Jul 2011 10:36:27 +0200 [thread overview]
Message-ID: <201107031036.28186.rjw@sisk.pl> (raw)
In-Reply-To: <20110703102137.302ac415@schatten.dmk.lab>
On Sunday, July 03, 2011, Florian Mickler wrote:
> On Sun, 3 Jul 2011 08:58:41 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> > On Saturday, July 02, 2011, Andrea Righi wrote:
> > > Implement acpi_os_create_lock() as a C-preprocessor macro to assign
> > > unique lock_class_key to dynamically allocated locks and suppress wrong
> > > lockdep warnings.
> > >
> > > This fixes:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=38152
> > >
> > > Reported-by: Borislav Petkov <bp@alien8.de>
> > > Signed-off-by: Andrea Righi <andrea@betterlinux.com>
> >
> > So, how exactly does it work?
>
> The spin_lock_init macro stringifies it's argument and uses that as a
> name for the lock in the debugging.
>
> By re-executing spin_lock_init (have not checked if that harms
> anything, but it should be ok) in the _macro_ the key changes from
> "lock" for all three locks to the actual argument
> "&acpi_gbl_global_lock_pending_lock", "&acpi_gbl_gpe_lock" or
> "&acpi_gbl_hardware_lock".
OK, thanks for the explanation.
The proposed solution doesn't seem to be extremely straightforward,
but perhaps it's the simplest one. I need to think about it a bit more.
Thanks,
Rafael
prev parent reply other threads:[~2011-07-03 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 15:31 [PATCH] ACPI: fix acpi_power_off lockdep splat Andrea Righi
2011-07-03 6:58 ` Rafael J. Wysocki
2011-07-03 8:21 ` Florian Mickler
2011-07-03 8:35 ` Andrea Righi
2011-07-03 8:36 ` Rafael J. Wysocki [this message]
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=201107031036.28186.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=andrea@betterlinux.com \
--cc=bp@alien8.de \
--cc=florian@mickler.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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