From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: 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: Tue, 13 Dec 2005 07:33:28 +1100 [thread overview]
Message-ID: <1134419609.6989.116.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.64.0512120909460.15597@g5.osdl.org>
> 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.
Sure, though I assumed it had already be tracked down at least partially
by Brian ;)
> Also, enabling DEBUG_PAGEALLOC might help, but that's not available on
> powerpc.
Remind me what is needed to get that working ? Unmapping of linear
mapping pages ? (I suppose I could do that if I also disable using large
pages for it).
> 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.
>
> Linus
next prev parent reply other threads:[~2005-12-12 20:35 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
2005-12-12 18:51 ` Jens Axboe
2005-12-12 20:33 ` Benjamin Herrenschmidt [this message]
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=1134419609.6989.116.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox