From: Jens Axboe <axboe@kernel.dk>
To: Florian Mickler <florian@mickler.org>
Cc: Martin Pirker <lkml.collector@gmail.com>,
Dan Carpenter <error27.lkml@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Wu Fengguang <fengguang.wu@intel.com>,
Richard Kennedy <richard@rsk.demon.co.uk>,
mjg@redhat.com
Subject: Re: 2.6.35-rc5 inconsistent lock state
Date: Sat, 04 Sep 2010 09:17:48 +0200 [thread overview]
Message-ID: <4C81F29C.7030600@kernel.dk> (raw)
In-Reply-To: <20100903093755.6fa13d4f@schatten.dmk.lab>
On 09/03/2010 09:37 AM, Florian Mickler wrote:
> On Mon, 19 Jul 2010 21:48:04 +0200
> Martin Pirker <lkml.collector@gmail.com> wrote:
>
>> On Sat, Jul 17, 2010 at 9:50 PM, Jens Axboe <axboe@kernel.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
next prev parent reply other threads:[~2010-09-04 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 20:33 2.6.35-rc5 inconsistent lock state Martin Pirker
2010-07-14 21:04 ` Rafael J. Wysocki
2010-07-17 19:04 ` Dan Carpenter
2010-07-17 19:50 ` Jens Axboe
2010-07-18 17:56 ` Martin Pirker
2010-07-19 0:39 ` Jens Axboe
2010-07-19 0:42 ` Jens Axboe
2010-07-19 19:48 ` Martin Pirker
2010-09-03 7:37 ` Florian Mickler
2010-09-04 7:17 ` Jens Axboe [this message]
2010-09-04 8:48 ` Florian Mickler
2010-07-15 17:38 ` Maciej Rutecki
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=4C81F29C.7030600@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=error27.lkml@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=florian@mickler.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml.collector@gmail.com \
--cc=miklos@szeredi.hu \
--cc=mjg@redhat.com \
--cc=richard@rsk.demon.co.uk \
--cc=rjw@sisk.pl \
/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