public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Mickler <florian@mickler.org>
To: Jens Axboe <axboe@kernel.dk>
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, 4 Sep 2010 10:48:44 +0200	[thread overview]
Message-ID: <20100904104844.1138b5af@schatten.dmk.lab> (raw)
In-Reply-To: <4C81F29C.7030600@kernel.dk>

On Sat, 04 Sep 2010 09:17:48 +0200
Jens Axboe <axboe@kernel.dk> wrote:

> 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?
> 
No, I just followed up the bug report from bug #16400[1]. I'm closing
it now. (It was marked as "resolved", which surfaces as "pending"
in Rafael's reports.)

Thx,
Flo

[1] https://bugzilla.kernel.org/show_bug.cgi?id=16400

p.s.: well, I'm closing it as soon as the bugzilla is available again. 

  reply	other threads:[~2010-09-04  8:48 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
2010-09-04  8:48             ` Florian Mickler [this message]
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=20100904104844.1138b5af@schatten.dmk.lab \
    --to=florian@mickler.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=error27.lkml@gmail.com \
    --cc=fengguang.wu@intel.com \
    --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