[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOJsxLG7fWuHeh-KXzG1PHwZRWztQQYvmxgn_97aYBCtqrLWug@mail.gmail.com>
Date: Tue, 10 Jul 2012 22:45:57 +0300
From: Pekka Enberg <penberg@...nel.org>
To: Christoph Lameter <christoph@...uxfoundation.org>
Cc: "wfg@...ux.intel.com" <wfg@...ux.intel.com>,
Christoph Lameter <cl@...ux.com>,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Early crashed kernel on CONFIG_SLOB
On Jul 10, 2012, at 6:17, wfg@...ux.intel.com wrote:
>> 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
On Tue, Jul 10, 2012 at 9:37 PM, Christoph Lameter
<christoph@...uxfoundation.org> wrote:
> I sent a patch yesterday (or was it friday) to fix the issue. Sorry @airport right now.
Which patch is that? I can't seem to find it.
--
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