From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org, dimetrios@gmail.com,
David Miller <davem@davemloft.net>
Subject: Re: Fw: [Bug 32772] New: PROBLEM: kernel BUG at net/ipv4/inetpeer.c:386
Date: Wed, 06 Apr 2011 18:25:23 +0200 [thread overview]
Message-ID: <1302107123.3209.113.camel@edumazet-laptop> (raw)
In-Reply-To: <1302105923.3209.103.camel@edumazet-laptop>
Le mercredi 06 avril 2011 à 18:05 +0200, Eric Dumazet a écrit :
>
> This reminds me a possible memory corruption (from another layer)
>
I found the reference of a past bug report, where slub_nomerge was used
too.
http://www.spinics.net/lists/netdev/msg154206.html
next prev parent reply other threads:[~2011-04-06 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 15:18 Fw: [Bug 32772] New: PROBLEM: kernel BUG at net/ipv4/inetpeer.c:386 Stephen Hemminger
2011-04-06 16:05 ` Eric Dumazet
2011-04-06 16:25 ` Eric Dumazet [this message]
2011-04-06 18:15 ` Dmitry Novikov
2011-04-06 18:16 ` David Miller
2011-04-13 20:14 ` Dmitry Novikov
2011-04-13 20:24 ` David Miller
2011-04-14 13:02 ` Dmitry Novikov
2011-04-14 13:32 ` 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=1302107123.3209.113.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=dimetrios@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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