From: Eric Sesterhenn <snakebyte@gmx.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, Chris Wright <chrisw@sous-sol.org>,
James Morris <jmorris@namei.org>,
William Lee Irwin III <wli@holomorphy.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: Redzone overwritten with CONFIG_SECURITY
Date: Tue, 27 May 2008 18:11:48 +0200 [thread overview]
Message-ID: <20080527161148.GA7291@alice> (raw)
In-Reply-To: <20080527151136.GA20750@alice>
* Eric Sesterhenn (snakebyte@gmx.de) wrote:
> * Pekka Enberg (penberg@cs.helsinki.fi) wrote:
>
> I am currently trying to reproduce this with SLAB as Vegard
> suggested for the kmemcheck report. After this I'll retest this
> on a fresh tree to make sure it isnt something buggy on my part
> and try some older kernels.
ok, with CONFIG_SECURITY, SLAB and CONFIG_DEBUG_SLAB on the
-rc3 based kmemcheck tree enabled i dont get any error.
I am currently building a fresh -rc4 (with SLUB) to make
sure this is for real, then i'll try that again with SLAB
and then start testing older kernels.
Greetings, Eric
next prev parent reply other threads:[~2008-05-27 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 14:34 Redzone overwritten with CONFIG_SECURITY Eric Sesterhenn
2008-05-27 14:00 ` Eric Sesterhenn
2008-05-27 14:23 ` Vegard Nossum
2008-05-27 14:53 ` Eric Sesterhenn
2008-05-27 14:55 ` Pekka Enberg
2008-05-27 15:00 ` Pekka Enberg
2008-05-27 15:11 ` Eric Sesterhenn
2008-05-27 16:11 ` Eric Sesterhenn [this message]
2008-05-27 17:59 ` Pekka Enberg
2008-05-27 18:04 ` Christoph Lameter
2008-05-27 17:47 ` Chris Wright
2008-05-28 10:03 ` Eric Sesterhenn
2008-05-28 21:51 ` Chris Wright
2008-05-31 23:24 ` Chris Wright
2008-05-27 18:25 ` Pekka Enberg
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=20080527161148.GA7291@alice \
--to=snakebyte@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.com \
--cc=wli@holomorphy.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