[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080527151136.GA20750@alice>
Date: Tue, 27 May 2008 17:11:36 +0200
From: Eric Sesterhenn <snakebyte@....de>
To: Pekka Enberg <penberg@...helsinki.fi>
Cc: linux-kernel@...r.kernel.org, Chris Wright <chrisw@...s-sol.org>,
James Morris <jmorris@...ei.org>,
William Lee Irwin III <wli@...omorphy.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Vegard Nossum <vegard.nossum@...il.com>
Subject: Re: Redzone overwritten with CONFIG_SECURITY
* Pekka Enberg (penberg@...helsinki.fi) wrote:
> (added some cc's)
>
> On Mon, May 26, 2008 at 5:34 PM, Eric Sesterhenn <snakebyte@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists