public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 17:11:36 +0200	[thread overview]
Message-ID: <20080527151136.GA20750@alice> (raw)
In-Reply-To: <84144f020805270800l5911ed02ia7a92d96a8aa32a7@mail.gmail.com>

* Pekka Enberg (penberg@cs.helsinki.fi) wrote:
> (added some cc's)
> 
> On Mon, May 26, 2008 at 5:34 PM, Eric Sesterhenn <snakebyte@gmx.de> wrote:
> > i enabled CONFIG_SECURITY on current git and get tons of
> > Redzone overwritten errors during early boot, even
> > with CONFIG_SECURITY_CAPABILITIES and CONFIG_SECURITY_NETWORK
> > disabled. After a while it ends with a kernel panic
> > saying: not syncing: Out of memory and no killable process...
> > Root partition is ext3 format.
> 
> So what kernel version is this and what's the last known version that
> worked? As it's early boot crash, maybe you can try to do git bisect
> on it?


this is 2.6.26-rc4, i didnt test any earlier versions so far
(ok, i did test some pre -rc4 git versions i think 4 days
ago, but they also showed the problem) this is the
first time that i enabled CONFIG_SECURITY on my testbox.

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.

Greetings, Eric

  reply	other threads:[~2008-05-27 15:11 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 [this message]
2008-05-27 16:11     ` Eric Sesterhenn
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=20080527151136.GA20750@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