From: David Miller <davem@davemloft.net>
To: Valdis.Kletnieks@vt.edu
Cc: ilpo.jarvinen@helsinki.fi, gilad@codefidence.com,
eric.dumazet@gmail.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
ori@comsleep.com
Subject: Re: 2.6.32-rc5-mmotm1101 - kernel BUG at net/ipv4/tcp_input.c:3707!
Date: Tue, 03 Nov 2009 18:34:35 -0800 (PST) [thread overview]
Message-ID: <20091103.183435.209882374.davem@davemloft.net> (raw)
In-Reply-To: <7916.1257300093@turing-police.cc.vt.edu>
From: Valdis.Kletnieks@vt.edu
Date: Tue, 03 Nov 2009 21:01:33 -0500
> Why was this blowing chunks in the IPv6 when I was making an IPv4 connection
> then? I just noticed that. My fetchmail can't make an IPv6 TCP connection to
> our IMAP server because the server isn't v6-enabled yet. And although I
> contact our DNS over IPv6, but that's UDP not TCP.
Many things IPV6 capable will go through the IPV4 compat
path of the IPV6 stack, depending upon how listening sockets
configure themselves etc.
next prev parent reply other threads:[~2009-11-04 2:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 17:50 Valdis.Kletnieks
2009-11-03 18:02 ` Eric Dumazet
2009-11-03 19:20 ` Gilad Ben-Yossef
2009-11-03 21:34 ` Ilpo JÀrvinen
2009-11-04 2:01 ` Valdis.Kletnieks
2009-11-04 2:34 ` David Miller [this message]
2009-11-04 6:38 ` Gilad Ben-Yossef
2009-11-04 16:40 ` [PATCH testing] Do not call IPv4 specific func in tcp_check_req Gilad Ben-Yossef
2009-11-05 7:22 ` David Miller
2009-11-04 16:43 ` 2.6.32-rc5-mmotm1101 - kernel BUG at net/ipv4/tcp_input.c:3707! Gilad Ben-Yossef
2009-11-05 2:33 ` Valdis.Kletnieks
2009-11-05 7:25 ` David Miller
2009-11-05 7:22 ` David Miller
2009-11-04 6:27 ` Gilad Ben-Yossef
2009-11-03 19:21 ` [PATCH 1/1] Use defaults when no route options are available Gilad Ben-Yossef
2009-11-04 13:28 ` David Miller
2009-11-04 14:27 ` Gilad Ben-Yossef
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=20091103.183435.209882374.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=gilad@codefidence.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ori@comsleep.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
all inboxes | Powered by JetHome®