[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2517820.omWyusa00U@cpaasch-mac>
Date: Sun, 07 Apr 2013 16:37:04 +0200
From: Christoph Paasch <christoph.paasch@...ouvain.be>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Hannes Frederic Sowa <hannes@...essinduktion.org>,
Tetja Rediske <tetja@...ja.de>, djduanjiong@...il.com,
netdev@...r.kernel.org, steffen.klassert@...unet.com,
Neal Cardwell <ncardwell@...gle.com>,
David Miller <davem@...emloft.net>
Subject: Re: PROBLEM: IPv6 TCP-Connections resetting
On Saturday 06 April 2013 10:54:39 Eric Dumazet wrote:
> OK, it seems bug was added in commit
> ec18d9a2691d69cd14b48f9b919fddcef28b7f5c
> (ipv6: Add redirect support to all protocol icmp error handlers.)
>
> Not sure why Tetja Rediske bisected to
> 093d04d42fa094f6740bb188f0ad0c215ff61e2c
I made a setup to trigger the ICMPv6 Redirect.
Yes, the bug was added by ec18d9a26 (ipv6: Add redirect support to all
protocol icmp error handlers.), but prior to 093d04d4 (ipv6: Change skb->data
before using icmpv6_notify() to propagate redirect) the stack did not enter
tcp_v6_err upon a redirect message.
This, because inside icmpv6_notify, skb->data did not point to the inner IP
header. So, when icmpv6_notify looks up the protocol-handler, it will not
match on tcp_v6_err.
> Could you send a patch with this single line change (no cleanup), and
> a more detailed changelog, once the bug origin is clearly identified ?
Yes, will resend.
Cheers,
Christoph
--
IP Networking Lab --- http://inl.info.ucl.ac.be
MultiPath TCP in the Linux Kernel --- http://multipath-tcp.org
UCLouvain
--
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists