[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20151208.211534.626369766229141448.davem@davemloft.net>
Date: Tue, 08 Dec 2015 21:15:34 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: Valdis.Kletnieks@...edu
Cc: fw@...len.de, netfilter-devel@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
pablo@...filter.org
Subject: Re: next-20151207 - crash in IPv6 code
From: Valdis.Kletnieks@...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.Kletnieks@...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 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/
Powered by blists - more mailing lists