LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hans de Bruin <jmdebruin@xmsnet.nl>
To: LKML <linux-kernel@vger.kernel.org>, jesse@nicira.com
Subject: [regression] 2.6.37+ commit 0363466866d9.... breaks tcp ipv6
Date: Tue, 18 Jan 2011 20:52:04 +0100 [thread overview]
Message-ID: <4D35EF64.1040906@xmsnet.nl> (raw)
In-Reply-To: <4D335417.80704@xmsnet.nl>
On 01/16/2011 09:24 PM, Hans de Bruin wrote:
> After last nights compile i lost the possibility to connect to ssh and
> http over ipv6. The connection stops at syn_sent. connections to my
> machine end in syn_recv. ping6 still works.
>
The bisect ended in:
0363466866d901fbc658f4e63dd61e7cc93dd0af is the first bad commit
commit 0363466866d901fbc658f4e63dd61e7cc93dd0af
Author: Jesse Gross <jesse@nicira.com>
Date: Sun Jan 9 06:23:35 2011 +0000
net offloading: Convert checksums to use centrally computed features.
In order to compute the features for other offloads (primarily
scatter/gather), we need to first check the ability of the NIC to
offload the checksum for the packet. Since we have already computed
this, we can directly use the result instead of figuring it out
again.
Signed-off-by: Jesse Gross <jesse@nicira.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
ssh ::1 still works. And since dns still works I guess udp is not
affected. My nic is a:
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752
Gigabit Ethernet PCI Express (rev 02)
--
Hans
next prev parent reply other threads:[~2011-01-18 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 20:24 Possible ipv6 regression Hans de Bruin
2011-01-18 19:52 ` Hans de Bruin [this message]
2011-01-18 20:06 ` [regression] 2.6.37+ commit 0363466866d9.... breaks tcp ipv6 Jesse Gross
2011-01-18 21:42 ` Hans de Bruin
2011-01-18 22:03 ` Eric Dumazet
2011-01-19 13:17 ` Hans de Bruin
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=4D35EF64.1040906@xmsnet.nl \
--to=jmdebruin@xmsnet.nl \
--cc=jesse@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [regression] 2.6.37+ commit 0363466866d9.... breaks tcp ipv6' \
/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
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).