From: Dave Jones <davej@redhat.com>
To: Jens Axboe <axboe@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: .17rc5 cfq slab corruption.
Date: Tue, 30 May 2006 10:13:18 -0400 [thread overview]
Message-ID: <20060530141318.GH14721@redhat.com> (raw)
In-Reply-To: <20060530135224.GA3179@redhat.com>
On Tue, May 30, 2006 at 09:52:24AM -0400, Dave Jones wrote:
> On Tue, May 30, 2006 at 03:50:59PM +0200, Jens Axboe wrote:
>
> > > > > > Pretty baffling... cfq has been hammered pretty thoroughly over the
> > > > > > last months and _nothing_ has shown up except some performance anomalies
> > > > > > that are now fixed. Since daves case (at least) seems to be
> > > > > > use-after-free, I'll see if I can reproduce with some contrived case.
> > > > > > I'm asuming that picasa forks and exits a lot with submitted io in
> > > > > > between than may not have finished at exit.
> > > > >
> > > > > The second time I hit it, was actually during boot up.
> > > >
> > > > Dave, do you have any io scheduler switching going on?
> > >
> > > Nope, everything set to use CFQ as default, and left that way.
> >
> > Hrmpf ok, I had hoped perhaps something in your init scripts modified
> > the scheduler value.
>
> grep doesn't show anything in init scripts, and ttbomk, hald isn't messing
> with this. (Actually I'm seeing it trigger before that gets started
> anyway, so that can't be it).
In case it makes a difference to help with reproducing -- the hardware of this
system is:
two sata drives sda1/sdb1 in single-volume device-mapper configuration as VolGroup00-LogVol00
pata cd drive on /dev/hdc
usb memory stick on sdc1
Nothing too out of the ordinary there..
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-05-30 14:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 21:39 .17rc5 cfq slab corruption Dave Jones
2006-05-27 0:00 ` Andrew Morton
2006-05-27 7:07 ` Jens Axboe
2006-05-27 13:31 ` Dave Jones
2006-05-27 14:52 ` Jens Axboe
2006-05-30 13:17 ` Jens Axboe
2006-05-30 13:44 ` Dave Jones
2006-05-30 13:50 ` Jens Axboe
2006-05-30 13:52 ` Dave Jones
2006-05-30 14:13 ` Dave Jones [this message]
2006-05-30 16:12 ` Dave Jones
2006-05-30 16:49 ` Jens Axboe
2006-05-30 16:56 ` Dave Jones
2006-05-30 17:04 ` Jens Axboe
2006-05-30 18:49 ` Jens Axboe
2006-05-30 18:51 ` Jens Axboe
2006-05-30 19:11 ` Jens Axboe
2006-05-30 19:23 ` Dave Jones
2006-05-30 19:27 ` Jens Axboe
2006-05-30 19:28 ` OGAWA Hirofumi
2006-05-30 19:42 ` Jens Axboe
2006-05-30 19:48 ` Jens Axboe
2006-05-30 19:49 ` OGAWA Hirofumi
2006-05-27 2:56 ` Dave Jones
2006-05-27 3:03 ` Dave Jones
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=20060530141318.GH14721@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.