mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@suse.de>
Subject: Re: 2.6.17-rc4-mm3 cfq oops->panic w. fs damage
Date: Mon, 29 May 2006 13:00:40 +0200	[thread overview]
Message-ID: <1148900440.9817.46.camel@homer> (raw)
In-Reply-To: <1148804675.7755.2.camel@homer>

On Sun, 2006-05-28 at 10:24 +0200, Mike Galbraith wrote: 
> On Sun, 2006-05-28 at 10:03 +0200, Mike Galbraith wrote:
> 
> > Yup, mm3 makes reliable kaboom.
> > 
> > I suppose the first thing to do is see if it's cfq, and then maybe toss
> > a dart at the patch list.
> 
> That was too easy.  It's git-cfq.patch.

Too easy indeed.

After staring at these changes, and not having anything poke me in the
eye that looked like it might cause list corruption, I decided to try
them in a different kernel.  I put them into 2.6.16-rt25, and there they
work peachy.  A diff of 2.6.16-rt25+git-cfq.patch->2.6.17-rc4-mm3 shows
what I was expecting (locking changes), but it's embedded in ~1000 lines
of diff, and doesn't look particularly trivial.

Hi Jens <punt> :)

	-Mike


  reply	other threads:[~2006-05-29 10:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28  5:12 Mike Galbraith
2006-05-28  5:25 ` Al Viro
2006-05-28  6:00   ` Mike Galbraith
2006-05-28  7:48     ` Mike Galbraith
2006-05-28  8:03       ` Mike Galbraith
2006-05-28  8:24         ` Mike Galbraith
2006-05-29 11:00           ` Mike Galbraith [this message]
2006-05-30 12:36             ` Jens Axboe
2006-05-30 13:27               ` Mike Galbraith
2006-05-30 13:30                 ` 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=1148900440.9817.46.camel@homer \
    --to=efault@gmx.de \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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

Powered by JetHome