From: valdis.kletni...@vt.edu Date: Tue, 08 Dec 2015 16:54:17 -0500 > On Tue, 08 Dec 2015 12:34:09 +0100, Florian Westphal said: >> Valdis Kletnieks <valdis.kletni...@vt.edu> wrote: >> >> [ CC Pablo ] >> >> > Seen this in 2 boots out of two on next-20151207 when IPV6 networking >> > was available. It was stable when no net was available. Also, >> > next-20161127 is OK. >> > Haven't bisected it yet - this ring any bells? >> >> Thanks for the report, my fault -- its caused by >> 029f7f3b8701cc7aca8bdb which is only in Pablos nf-next tree. >> >> This should fix this bug (proper patch w. changelog coming >> after more testing): >> >> diff --git a/net/ipv6/netfilter/nf_conntrack_reasm.c >> b/net/ipv6/netfilter/nf_conntrack_reasm.c > > Pumped about 100M of IPv6 traffic through, and no problems. > > Feel free to stick a Reported-by:/Tested-By: on this patch...
Thanks for testing. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
