You have a genuine, reproducible method of crashing the kernel. I think that does deserve a PR.
You could also do a custom kernel compilation with options INVARIANTS and options INVARIANT_SUPPORT.
There are some KASSERTs in the code which could give a hint what is happening in in_fib.c.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.