Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753788AbaAaCRB (ORCPT ); Thu, 30 Jan 2014 21:17:01 -0500 Received: from mail-ig0-f178.google.com ([209.85.213.178]:65485 "EHLO mail-ig0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753418AbaAaCQ7 (ORCPT ); Thu, 30 Jan 2014 21:16:59 -0500 Message-ID: <1391134615.28432.83.camel@edumazet-glaptop2.roam.corp.google.com> Subject: Re: kmem_cache_alloc panic in 3.10+ From: Eric Dumazet To: dormando Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Alexei Starovoitov Date: Thu, 30 Jan 2014 18:16:55 -0800 In-Reply-To: References: <1390062576.31367.519.camel@edumazet-glaptop2.roam.corp.google.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2014-01-29 at 23:05 -0800, dormando wrote: > We hit the routing code fairly hard. Any hints for what to look at or how > to instrument it? Or if it's fixed already? It's a real pain to iterate > since it takes ~30 days to crash, usually. Sometimes. I really wonder... it looks like a possible in SLUB. (might be already fixed) Could you try using SLAB instead ? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/