From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751512Ab2GJShk (ORCPT ); Tue, 10 Jul 2012 14:37:40 -0400 Received: from mail-gg0-f174.google.com ([209.85.161.174]:42494 "EHLO mail-gg0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751097Ab2GJShj convert rfc822-to-8bit (ORCPT ); Tue, 10 Jul 2012 14:37:39 -0400 References: <20120710111756.GA11351@localhost> In-Reply-To: <20120710111756.GA11351@localhost> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset=us-ascii Message-Id: Cc: Christoph Lameter , Pekka Enberg , Linux Memory Management List , LKML X-Mailer: iPad Mail (9B206) From: Christoph Lameter Subject: Re: linux-next: Early crashed kernel on CONFIG_SLOB Date: Tue, 10 Jul 2012 13:37:35 -0500 To: "wfg@linux.intel.com" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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@linux.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 > Date: Wed Jun 13 10:24:57 2012 -0500 > > mm, sl[aou]b: Extract common fields from struct kmem_cache > > Thanks, > Fengguang > >