From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: kernel 2.6.37 : oops in cleanup_once Date: Mon, 14 Mar 2011 14:14:24 +0100 Message-ID: <1300108464.3423.1.camel@edumazet-laptop> References: <4D491B8D.1000107@univ-nantes.fr> <1296643972.20445.9.camel@edumazet-laptop> <1296645887.20445.11.camel@edumazet-laptop> <4D495765.4090806@univ-nantes.fr> <1296658407.20445.19.camel@edumazet-laptop> <4D49726C.6020103@univ-nantes.fr> <1296659336.20445.22.camel@edumazet-laptop> <4D7DF1A3.6020501@univ-nantes.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel@vger.kernel.org, netdev To: Yann Dupont Return-path: Received: from mail-bw0-f46.google.com ([209.85.214.46]:36686 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751959Ab1CNNO3 (ORCPT ); Mon, 14 Mar 2011 09:14:29 -0400 In-Reply-To: <4D7DF1A3.6020501@univ-nantes.fr> Sender: netdev-owner@vger.kernel.org List-ID: Le lundi 14 mars 2011 =C3=A0 11:44 +0100, Yann Dupont a =C3=A9crit : > Le 02/02/2011 16:08, Eric Dumazet a =C3=A9crit : >=20 >=20 > > I suspect a mem corruption from another layer (not inetpeer) > > > > Unfortunately many kmem caches share the "64 bytes" cache. > > > > Could you please add "slub_nomerge" on your boot command ? > > > ... >=20 > > > >> -Is there a very severe impact on performance ? > >> > > not at all > > > Maybe there is an impact after all : since then, we don't have proble= ms=20 > anymore ! >=20 > linkwood:~# uptime > 11:42:03 up 39 days, 17:08, 3 users, load average: 0.01, 0.03, 0.= 05 >=20 > So... could slub_nomerge hide or simply avoid the problem ? > Or are we just lucky this time ? >=20 >=20 I would say you are lucky ;) Not all memory corruptions are noticed. Sometimes it touch unused parts of memory, or some parts with no critical content.