On Tue, 3 Nov 2009, Gilad Ben-Yossef wrote:I agree, but for my defense I should add this was not just plain carelessness, I believed
Eric Dumazet wrote:
Valdis.Kletnieks@xxxxxx a écrit :Bah... this is most probably my fault. Sorry about that.
Seen right after I started 'fetchmail'. Reproducible - 3 out of 3.
I'll bisect this tonight if nobody jumps up and yells they know what it
is...
Can you please try the patch in the next email?
But also, can you please send me the route table in effect when this happened
and the fetchmail command line/config (removing any passwords or account
details of course)? I want to understand better when this happens.
According to the stacktrace, it came from ipv6 side which doesn't have any null checking what so ever atm (you only handled ipv4 correctly). ...You should be a bit more careful next time when adding any BUG_ONs...