From: Matt Mackall <mpm@selenic.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
Andrew Morton <akpm@osdl.org>
Subject: Re: + stack-corruption-detector.patch added to -mm tree
Date: Sun, 19 Mar 2006 14:52:32 -0600 [thread overview]
Message-ID: <20060319205232.GA31656@waste.org> (raw)
In-Reply-To: <1142798807.3018.29.camel@laptopd505.fenrus.org>
On Sun, Mar 19, 2006 at 09:06:46PM +0100, Arjan van de Ven wrote:
> On Sun, 2006-03-19 at 12:26 -0600, Matt Mackall wrote:
> > On Wed, Mar 08, 2006 at 10:16:50PM -0500, Rik van Riel wrote:
> > > On Wed, 8 Mar 2006, akpm@osdl.org wrote:
> > >
> > > > - memset(ret, 0, THREAD_SIZE); \
> > > > + memset(ret, 0x55, THREAD_SIZE); \
> > >
> > > Xen uses 0x55 as a poison pattern too. I wonder if we should
> > > change this one (this one's newer ;)) to something else.
> >
> > I think we should have a central poison.h file.
>
> sure
>
> but it's not like xen is anywhere near mergable, so xen should change if
> anything ;)
Well Xen is a separate problem. But figuring out what poison value
came from where and which values are already used is getting to be an
ugly problem for the kernel itself.
--
Mathematics is the supreme nostalgia of our time.
prev parent reply other threads:[~2006-03-19 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603082041.k28Kf7H1027435@shell0.pdx.osdl.net>
2006-03-09 3:16 ` + stack-corruption-detector.patch added to -mm tree Rik van Riel
2006-03-19 18:26 ` Matt Mackall
2006-03-19 20:06 ` Arjan van de Ven
2006-03-19 20:52 ` Matt Mackall [this message]
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=20060319205232.GA31656@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.com \
/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