[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C81F29C.7030600@kernel.dk>
Date: Sat, 04 Sep 2010 09:17:48 +0200
From: Jens Axboe <axboe@...nel.dk>
To: Florian Mickler <florian@...kler.org>
CC: Martin Pirker <lkml.collector@...il.com>,
Dan Carpenter <error27.lkml@...il.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Miklos Szeredi <miklos@...redi.hu>,
Wu Fengguang <fengguang.wu@...el.com>,
Richard Kennedy <richard@....demon.co.uk>, mjg@...hat.com
Subject: Re: 2.6.35-rc5 inconsistent lock state
On 09/03/2010 09:37 AM, Florian Mickler wrote:
> On Mon, 19 Jul 2010 21:48:04 +0200
> Martin Pirker <lkml.collector@...il.com> wrote:
>
>> On Sat, Jul 17, 2010 at 9:50 PM, Jens Axboe <axboe@...nel.dk> wrote:
>>> I posted a patch for this the other day, but I just now notice
>>> that it was a private list of CC addresses.
>>>
>>> Can anyone try this completed untested patch?
>>
>> [sorry Jens for my first failed test attempt, my idiocy...]
>>
>> applied to 2.6.35-rc5 -> error message so far not seen again.
>> about functionality, well, HD spin up control via laptop_mode I cannot
>> say, I've a SSD...
>>
>> HTH,
>> Martin
>
> Is this patch on route to mainline? Or did this get fixed some other
> way?
The lock is bh safe in mainline now, the patch should not be
needed. Are you still seeing the bad behaviour?
--
Jens Axboe
--
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