ping6 cause kernel panic in nd6_output_lle()

Previous thread: CACHE_LINE_SIZE too small, so struct vpglocks size alignment doesn't work by Svatopluk Kraus on Friday, October 1, 2010 - 6:00 am. (3 messages)

Next thread: Very interesting paper: An Analysis of Linux Scalability to many Cores by Andre Oppermann on Friday, October 1, 2010 - 12:05 pm. (1 message)
From: Andrey Chernov
Date: Friday, October 1, 2010 - 6:59 am

Pinging nonexistent IPv6 adress withing the same prefixlen 64 (i.e. 
nonexistent neighbor) immediately cause kernel panic in nd6_output_lle()

See
http://img837.imageshack.us/img837/7496/01102010f.jpg

Please fix.

-- 
http://ache.pp.ru/
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
From: Bjoern A. Zeeb
Date: Friday, October 1, 2010 - 4:06 pm

want to try the patch from kern/148857?

/bz

-- 
Bjoern A. Zeeb                              Welcome a new stage of life.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
From: Andrey Chernov
Date: Saturday, October 2, 2010 - 6:39 am

For recent -current the patch have missing
struct mbuf *m = NULL; 
declaration early in the nd6_llinfo_timer().

Besides that, it fix the panic, thanx!

-- 
http://ache.pp.ru/
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Previous thread: CACHE_LINE_SIZE too small, so struct vpglocks size alignment doesn't work by Svatopluk Kraus on Friday, October 1, 2010 - 6:00 am. (3 messages)

Next thread: Very interesting paper: An Analysis of Linux Scalability to many Cores by Andre Oppermann on Friday, October 1, 2010 - 12:05 pm. (1 message)