From: David Miller <davem@davemloft.net>
To: grant.likely@secretlab.ca
Cc: devicetree-discuss@lists.ozlabs.org, tglx@linutronix.de,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: Fix locking vs. interrupts
Date: Wed, 12 Jun 2013 02:15:42 -0700 (PDT) [thread overview]
Message-ID: <20130612.021542.427308733208440842.davem@davemloft.net> (raw)
In-Reply-To: <20130612090612.7E4ED3E0A56@localhost>
From: Grant Likely <grant.likely@secretlab.ca>
Date: Wed, 12 Jun 2013 10:06:12 +0100
> On Wed, 12 Jun 2013 10:25:56 +0200 (CEST), Thomas Gleixner <tglx@linutronix.de> wrote:
>> On Wed, 12 Jun 2013, Benjamin Herrenschmidt wrote:
>>
>> > The OF code uses irqsafe locks everywhere except in a handful of functions
>> > for no obvious reasons. Since the conversion from the old rwlocks, this
>> > now triggers lockdep warnings when used at interrupt time. At least one
>> > driver (ibmvscsi) seems to be doing that from softirq context.
>> >
>> > This converts the few non-irqsafe locks into irqsafe ones, making them
>> > consistent with the rest of the code.
>>
>> Fun. https://lkml.org/lkml/2013/2/4/416 seems to have got lost
>>
>> > Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>> > CC: <stable@vger.kernel.org> [v3.9+]
>>
>> Acked-by: Thomas Gleixner <tglx@linutronix.de>
>>
>> > ---
>> >
>> > Note: It's silly to access the device-tree at interrupt time in most cases,
>> > and we should probably fix ibmvscsi, but for the time being, let's fix the
>>
>> Right.
>>
>> > obvious bug. Thomas, this can probably still go into 3.10... If not, I've
>> > CCed stable.
>>
>> Should go through Grant I think.
>
> Applied, thanks.
FWIW:
Acked-by: David S. Miller <davem@davemloft.net>
prev parent reply other threads:[~2013-06-12 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 5:39 [PATCH] of: Fix locking vs. interrupts Benjamin Herrenschmidt
2013-06-12 8:25 ` Thomas Gleixner
2013-06-12 8:56 ` Benjamin Herrenschmidt
2013-06-12 9:06 ` Grant Likely
2013-06-12 9:15 ` David Miller [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=20130612.021542.427308733208440842.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).