Bug 91491
Summary: | trie_leaf_remove | ||
---|---|---|---|
Product: | Networking | Reporter: | Yavuz Selim Komur (komur) |
Component: | IPV4 | Assignee: | Stephen Hemminger (stephen) |
Status: | NEW --- | ||
Severity: | blocking | CC: | alexander.h.duyck |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 3.14-2-amd64 #1 Debian 3.14.15-2.1khz | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Yavuz Selim Komur
2015-01-17 21:30:18 UTC
Do you happen to know what it was you did to trigger this? Are there any reproduction steps we might be able to take to reproduce this issue? Also is this something you have seen repeatedly or have you only ever seen this occur once? this is quagga router. receive full BGP route. We observe the last 6 months. Sometimes twice a month, sometimes twice a week. On Mon, 2015-01-26 at 23:18 +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=91491 > > Alexander Duyck <alexander.h.duyck@redhat.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |alexander.h.duyck@redhat.co > | |m > > --- Comment #1 from Alexander Duyck <alexander.h.duyck@redhat.com> --- > Do you happen to know what it was you did to trigger this? Are there any > reproduction steps we might be able to take to reproduce this issue? > > Also is this something you have seen repeatedly or have you only ever seen > this > occur once? > So the item of interest in all this is the value of RBX. I am fairly certain this represents the leaf->parent value with the least significant bit stripped to remove the leaf flag. I've gone though the code and I don't see any obvious spots where we would update a child without updating the parent pointer, or the parent without the child pointer. And most other spots we initialize the parent value to NULL. It leads me to wonder if there isn't a use after free bug floating around somewhere in the kernel that could be corrupting the leaves shortly after they are allocated. Do you know if this is the only call trace you ever see, or are there some other traces that this issue presents as in addition to this? Was 48 days. One more error did not occur. |