> typo in unlocking (causing recursive lock instead)
Fixed. Thanks.
> lack of inet6 support for inpcb locking, e.g. no
> handling of locks in in6_pcbdetach.
> attempts to destroy held lock in in_pcbdetach
Gurg, IPv6 isn't locked up yet! These must be the result of inadvertent
interactions with the shared IPv4 code. I'll see what can be done to
either mitigate the effects for IPv6 or quickly lock up v6.
Jeffrey
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
