linux-kernel - [regression] 2.6.37+ commit 0363466866d9.... breaks tcp ipv6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D35EF64.1040906@xmsnet.nl>
Date:	Tue, 18 Jan 2011 20:52:04 +0100
From:	Hans de Bruin <jmdebruin@...net.nl>
To:	LKML <linux-kernel@...r.kernel.org>, jesse@...ira.com
Subject: [regression] 2.6.37+ commit 0363466866d9.... breaks tcp ipv6

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@...ira.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@...ira.com>
     Signed-off-by: David S. Miller <davem@...emloft.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/