[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CF1C132D-2873-408A-BCC9-B9F57BE6EDDB@linuxfoundation.org>
Date: Tue, 10 Jul 2012 13:37:35 -0500
From: Christoph Lameter <christoph@...uxfoundation.org>
To: "wfg@...ux.intel.com" <wfg@...ux.intel.com>
Cc: Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Early crashed kernel on CONFIG_SLOB
I sent a patch yesterday (or was it friday) to fix the issue. Sorry @airport right now.
On Jul 10, 2012, at 6:17, wfg@...ux.intel.com wrote:
> Hi Christoph,
>
> This commit crashes the kernel w/o any dmesg output (the attached one
> is created by the script as a summary for that run). This is very
> reproducible in kvm for the attached config.
>
> commit 3b0efdfa1e719303536c04d9abca43abeb40f80a
> Author: Christoph Lameter <cl@...ux.com>
> Date: Wed Jun 13 10:24:57 2012 -0500
>
> mm, sl[aou]b: Extract common fields from struct kmem_cache
>
> Thanks,
> Fengguang
> <dmesg-kvm-waimea-2191-2012-07-10-17-32-01>
> <config-3.5.0-rc6+>
--
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