All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>, Jens Axboe <axboe@suse.de>,
	Brian King <brking@us.ibm.com>
Subject: Re: Memory corruption & SCSI in 2.6.15
Date: Mon, 12 Dec 2005 13:32:01 -0500	[thread overview]
Message-ID: <20051212183201.GA19599@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0512120909460.15597@g5.osdl.org>

Linus Torvalds wrote:
> 
> On Mon, 12 Dec 2005, Benjamin Herrenschmidt wrote:
> > 
> > Current -git as of today (that is 2.6.15-rc5 + the batch of fixes Linus
> > pulled after his return) was dying in weird ways for me on POWER5. I had
> > the good idea to activate slab debugging, and I now see it detecting
> > slab corruption as soon as the IPR driver initializes.
> > 
> > Since I remember seeing a discussion somewhere on a list between Brian
> > King and Jens Axboe about use-after-free problems in SCSI and possible
> > other niceties of that sort, I though it might be related...
> > 
> > Anything I can do to help track this down ?
> 
> If it's easily repeatable, doing a "git bisect" to see when it starts 
> happening is the obvious big sledge-hammer thing to try. Even if you don't 
> bisect all the way, just narrowing it down a bit more might help.

I manually narrowed this down to between 2.6.14-git14 (good) and
2.6.15-rc1 (bad).  Will try git bisection later today.

> There's a raid1 use-after-free bugfix that I just merged and pushed out, 
> but I doubt that one is relevant. But you might try to update.

FWIW, I'm hitting this in a non-raid setup.

  reply	other threads:[~2005-12-12 18:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12  7:13 Memory corruption & SCSI in 2.6.15 Benjamin Herrenschmidt
2005-12-12 17:17 ` Linus Torvalds
2005-12-12 18:32   ` Nathan Lynch [this message]
2005-12-12 18:51     ` Jens Axboe
2005-12-12 20:33   ` Benjamin Herrenschmidt
2005-12-12 20:51     ` Linus Torvalds
2005-12-12 20:57       ` Benjamin Herrenschmidt
2005-12-13  0:11       ` Benjamin Herrenschmidt
2005-12-12 18:09 ` Jens Axboe
2005-12-12 19:05 ` Brian King
2005-12-12 19:55   ` Linus Torvalds
2005-12-12 20:13     ` James Bottomley
2005-12-12 20:01   ` Nathan Lynch

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=20051212183201.GA19599@localhost.localdomain \
    --to=ntl@pobox.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=brking@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=torvalds@osdl.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.