From: Jens Axboe <axboe@suse.de>
To: Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: .17rc5 cfq slab corruption.
Date: Tue, 30 May 2006 21:27:08 +0200 [thread overview]
Message-ID: <20060530192708.GK4199@suse.de> (raw)
In-Reply-To: <20060530192355.GE17218@redhat.com>
On Tue, May 30 2006, Dave Jones wrote:
> On Tue, May 30, 2006 at 09:11:28PM +0200, Jens Axboe wrote:
>
> > > > > Just do a l *cfq_set_request+0x202 from gdb if you have
> > > > > CONFIG_DEBUG_INFO enabled in your vmlinux.
> > > >
> > > > Doh, found it. Dave, please try and reproduce with this applied:
> > >
> > > Nevermind, that's not it either. Damn. Stay tuned.
> >
> > Try this instead, please.
>
> Heh, I was waiting forever to get that debuginfo package downloaded & unpacked.
> I'll throw this into my next build, and see what happens.
> Is this likely to fix the slab corruption bug I first reported,
> or the list corruption as seen in the bugzilla, or (optimistically) both ?
Both, it's the same bug.
--
Jens Axboe
next prev parent reply other threads:[~2006-05-30 19:25 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
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 [this message]
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=20060530192708.GK4199@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--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.