From: Dave Jones <davej@redhat.com>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: more cfq spinlock badness
Date: Wed, 1 Feb 2006 11:15:41 -0500 [thread overview]
Message-ID: <20060201161541.GD5875@redhat.com> (raw)
In-Reply-To: <20060201110228.GS4215@suse.de>
On Wed, Feb 01, 2006 at 12:02:28PM +0100, Jens Axboe wrote:
> > > if you are using that? The bug above has in the
> > > past always been able to be explained by a driver destroying a structure
> > > embedding the queue lock before the queue is dead.
> >
> > as there were no ub devices plugged in at the time, I think
> > Pete is off the hook for this one.
>
> The ub fix hasn't been merged yet.
Really? I thought Pete synced up a whole bunch of ub bits including that already.
> Just trying to be absolutely certain
> that you didn't have that loaded?
99.9% sure. (It was a few days ago, and I'm already forgetting details).
Dave
next prev parent reply other threads:[~2006-02-01 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 6:39 more cfq spinlock badness Dave Jones
2006-01-31 9:09 ` Jens Axboe
2006-01-31 17:36 ` Dave Jones
2006-02-01 11:02 ` Jens Axboe
2006-02-01 16:15 ` Dave Jones [this message]
[not found] ` <mailman.1138828082.21892.linux-kernel2news@redhat.com>
2006-02-03 18:44 ` Pete Zaitcev
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=20060201161541.GD5875@redhat.com \
--to=davej@redhat.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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