From: John Dykstra <john.dykstra1@gmail.com>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
David Miller <davem@davemloft.net>,
mangoo@wpkg.org, netdev@vger.kernel.org
Subject: Re: WARNING: at net/ipv4/af_inet.c:155 inet_sock_destruct+0x122/0x13a()
Date: Thu, 13 Aug 2009 15:21:45 +0000 [thread overview]
Message-ID: <1250176905.7289.7.camel@Maple> (raw)
In-Reply-To: <4A831F69.1080703@hp.com>
On Wed, 2009-08-12 at 16:00 -0400, Vlad Yasevich wrote:
> BTW, I've seen the same issue in 2.6.28 and 2.6.29 while doing a bunch
> of NFS-over-UDP testing. I've seen the issue reported in 2.6.27 as well,
> but it went by ignored. It's not easy to reproduce as it seems like it
> requires quite a bit traffic over over multiple interfaces.
I've been unable to reproduce it so far. Has bonding always been
present in the cases you've seen, or are multiple independent interfaces
sufficient?
In the case you reported initially, openvpn was using UDP, but the peer
was dead, so there presumably wasn't much traffic from that app. Was
there lots of NFS-over-UDP traffic also going on?
Where was the independent report on 2.6.27?
-- John
next prev parent reply other threads:[~2009-08-13 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 8:30 WARNING: at net/ipv4/af_inet.c:155 inet_sock_destruct+0x122/0x13a() Tomasz Chmielewski
2009-08-04 0:38 ` John Dykstra
2009-08-04 4:20 ` David Miller
2009-08-04 6:18 ` Eric Dumazet
2009-08-12 20:00 ` Vlad Yasevich
2009-08-13 15:21 ` John Dykstra [this message]
2009-08-13 17:04 ` Vlad Yasevich
2009-08-13 18:16 ` Tomasz Chmielewski
2009-08-04 20:04 ` John Dykstra
2009-08-04 20:35 ` Tomasz Chmielewski
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=1250176905.7289.7.camel@Maple \
--to=john.dykstra1@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mangoo@wpkg.org \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.com \
/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;
as well as URLs for NNTP newsgroup(s).