[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20130612.021542.427308733208440842.davem@davemloft.net>
Date: Wed, 12 Jun 2013 02:15:42 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: grant.likely@...retlab.ca
Cc: tglx@...utronix.de, benh@...nel.crashing.org,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
devicetree-discuss@...ts.ozlabs.org
Subject: Re: [PATCH] of: Fix locking vs. interrupts
From: Grant Likely <grant.likely@...retlab.ca>
Date: Wed, 12 Jun 2013 10:06:12 +0100
> On Wed, 12 Jun 2013 10:25:56 +0200 (CEST), Thomas Gleixner <tglx@...utronix.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@...nel.crashing.org>
>> > CC: <stable@...r.kernel.org> [v3.9+]
>>
>> Acked-by: Thomas Gleixner <tglx@...utronix.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@...emloft.net>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists