On Sun, Sep 25, 2016 at 6:59 PM, Maciej Żenczykowski <zenczykow...@gmail.com> wrote: > + ifp->idev->cnf.rtr_solicits != 0 &&
Given that some of this patch checks for == -1, and some of it checks for != 0... is it possible that setting the value to something unexpected like -3 will cause any issues to the stack? (Other than just rendering IPv6 unusable on this interface, which seems like a given.)