From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yann Dupont <Yann.Dupont@univ-nantes.fr>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: kernel 2.6.37 : oops in cleanup_once
Date: Mon, 14 Mar 2011 14:14:24 +0100 [thread overview]
Message-ID: <1300108464.3423.1.camel@edumazet-laptop> (raw)
In-Reply-To: <4D7DF1A3.6020501@univ-nantes.fr>
Le lundi 14 mars 2011 à 11:44 +0100, Yann Dupont a écrit :
> Le 02/02/2011 16:08, Eric Dumazet a écrit :
>
>
> > 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 ?
> >
> ...
>
> >
> >> -Is there a very severe impact on performance ?
> >>
> > not at all
> >
> Maybe there is an impact after all : since then, we don't have problems
> anymore !
>
> linkwood:~# uptime
> 11:42:03 up 39 days, 17:08, 3 users, load average: 0.01, 0.03, 0.05
>
> So... could slub_nomerge hide or simply avoid the problem ?
> Or are we just lucky this time ?
>
>
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.
prev parent reply other threads:[~2011-03-14 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D491B8D.1000107@univ-nantes.fr>
2011-02-02 10:52 ` kernel 2.6.37 : oops in cleanup_once Eric Dumazet
2011-02-02 11:24 ` Eric Dumazet
2011-02-02 13:08 ` Yann Dupont
2011-02-02 14:53 ` Eric Dumazet
2011-02-02 15:04 ` Yann Dupont
2011-02-02 15:08 ` Eric Dumazet
2011-02-02 17:59 ` Yann Dupont
2011-03-14 10:44 ` Yann Dupont
2011-03-14 13:14 ` Eric Dumazet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1300108464.3423.1.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=Yann.Dupont@univ-nantes.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox