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: Wed, 02 Feb 2011 12:24:47 +0100 [thread overview]
Message-ID: <1296645887.20445.11.camel@edumazet-laptop> (raw)
In-Reply-To: <1296643972.20445.9.camel@edumazet-laptop>
Le mercredi 02 février 2011 à 11:52 +0100, Eric Dumazet a écrit :
> Le mercredi 02 février 2011 à 09:53 +0100, Yann Dupont a écrit :
> > Hello.
> > We recently upgraded one machine with vanilla 2.6.37, and experienced 2
> > kernel oops since. Each oops is after ~1 week of uptime.
> > The last oops was last night but we didn't had any trace.
oops, 2.6.37 "only"
> Yes this is a known problem.
>
> Please try commit 3408404a4c2a4eead9d73b0bbbfe3f225b65f492
> (inetpeer: Use correct AVL tree base pointer in inet_getpeer())
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3408404a4c2a4eead9d73b0bbbfe3f225b65f492
>
> I believe David will send it to stable team shortly, if not already
> done :)
Please ignore, this patch was for linux-2.6 tree, 2.6.37 was not
affected by the problem.
So its another problem... Is there anything particular you do on this
machine ?
next prev parent reply other threads:[~2011-02-02 11:24 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 [this message]
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
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=1296645887.20445.11.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