public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Neil Brown <neilb@suse.de>
Cc: Brad Campbell <brad@wasp.net.au>,
	Chuck Ebbert <cebbert@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] 2.6.21-rc6-git5 in cfq_dispatch_insert
Date: Wed, 25 Apr 2007 12:36:25 +0200	[thread overview]
Message-ID: <20070425103625.GU9715@kernel.dk> (raw)
In-Reply-To: <17967.11414.227668.186113@notabene.brown>

On Wed, Apr 25 2007, Neil Brown wrote:
> On Wednesday April 25, jens.axboe@oracle.com wrote:
> > 
> > Here's a fix for it, confirmed.
> > 
> 
> Patch looks good to me.

Good! And thanks for taking the time to look at this bug btw, it's had
me puzzled a bit this week. I should not have ruled out the aliases I
guess, they must be coming elsewhere than from O_DIRECT.

> Hopefully Brad can still wait for the WARN_ON to fire - it might give
> useful clues to why this is happening.  It might be interesting.

But he did and reported it about an hour ago, so all should be well.

-- 
Jens Axboe


  reply	other threads:[~2007-04-25 10:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 10:14 [OOPS] 2.6.21-rc6-git5 in cfq_dispatch_insert Brad Campbell
2007-04-15 10:49 ` Brad Campbell
2007-04-15 23:53   ` Adrian Bunk
2007-04-16  3:23     ` Brad Campbell
2007-04-16 22:39   ` Chuck Ebbert
2007-04-17  5:10     ` Neil Brown
2007-04-17  8:13       ` Brad Campbell
2007-04-17 11:48       ` Brad Campbell
2007-04-17 20:39       ` Bartlomiej Zolnierkiewicz
2007-04-18 12:37       ` Jens Axboe
2007-04-18 13:19         ` Brad Campbell
2007-04-18 13:21           ` Jens Axboe
2007-04-22  7:37             ` Brad Campbell
2007-04-23  7:35               ` Jens Axboe
2007-04-24 19:40                 ` Brad Campbell
2007-04-25  8:34                   ` Neil Brown
2007-04-25  8:46                     ` Jens Axboe
2007-04-25  9:34                       ` Jens Axboe
2007-04-25  9:37                       ` Neil Brown
2007-04-25  9:47                         ` Jens Axboe
2007-04-25 10:02                           ` Brad Campbell
2007-04-25 10:18                             ` Jens Axboe
2007-04-25 13:59                               ` Roland Kuhn
2007-04-25 10:25                           ` Neil Brown
2007-04-25 10:36                             ` Jens Axboe [this message]
2007-04-25  9:54                         ` Brad Campbell
2007-04-25  8:50                     ` Brad Campbell
2007-04-25 10:06                     ` Brad Campbell
2007-04-25 10:59                       ` Neil Brown
2007-04-25 11:17                         ` Degraded RAID performance - Was : " Brad Campbell
2007-04-18 13:19         ` Jens Axboe
     [not found] <79880979-51BB-4D28-A3E8-3AE0F56F5B0A@e18.physik.tu-muenchen.de>
     [not found] ` <20070424091807.GA3744@kernel.dk>
     [not found]   ` <6A6800B3-F9C8-4046-9E1C-A8CEA81B2CE0@e18.physik.tu-muenchen.de>
     [not found]     ` <20070424093904.GB3744@kernel.dk>
     [not found]       ` <20070424094003.GC3744@kernel.dk>
2007-04-24 12:27         ` Roland Kuhn
2007-04-24 12:32           ` Jens Axboe
2007-04-24 13:03             ` Roland Kuhn
2007-04-24 13:07               ` Jens Axboe

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=20070425103625.GU9715@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=brad@wasp.net.au \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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