Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1286869
| From | Valdis.Kletnieks@vt.edu |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: next-20151207 - crash in IPv6 code |
| Date | 2015-12-08 23:00 +0100 |
| Message-ID | <qDysG-7MA-3@gated-at.bofh.it> (permalink) |
| References | <qDiQW-6q2-13@gated-at.bofh.it> <qDoMF-1Ko-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Tue, 08 Dec 2015 12:34:09 +0100, Florian Westphal said: > Valdis Kletnieks <Valdis.Kletnieks@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...
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
next-20151207 - crash in IPv6 code Valdis Kletnieks <Valdis.Kletnieks@vt.edu> - 2015-12-08 06:20 +0100
Re: next-20151207 - crash in IPv6 code Florian Westphal <fw@strlen.de> - 2015-12-08 12:40 +0100
Re: next-20151207 - crash in IPv6 code Valdis.Kletnieks@vt.edu - 2015-12-08 23:00 +0100
Re: next-20151207 - crash in IPv6 code David Miller <davem@davemloft.net> - 2015-12-09 03:20 +0100
csiph-web