[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020805271059k11498424w3435b748f5254e2e@mail.gmail.com>
Date: Tue, 27 May 2008 20:59:44 +0300
From: "Pekka Enberg" <penberg@...helsinki.fi>
To: "Eric Sesterhenn" <snakebyte@....de>
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>,
"Christoph Lameter" <clameter@....com>
Subject: Re: Redzone overwritten with CONFIG_SECURITY
On Tue, May 27, 2008 at 7:11 PM, Eric Sesterhenn <snakebyte@....de> 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.
Then it's likely that we corrupt hugetlbfs_inode_cachep because of
SLUB merging and the real problem is somewhere else. Can you also try
passing 'slub_nomerge" as a kernel parameter with SLUB?
--
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