Re: locking errors in IPF in netbsd-6

[David Laight <david%l8s.co.uk@localhost>]

On Sun, Mar 10, 2013 at 11:28:27AM -0700, Chuck Silvers wrote:
> -/*                                                                         */
> -/* NOTE: It is by design that this function returns holding a read lock on */
> -/*       ipf_tokens.  Callers must make sure they release it!              */
>  /* ----------------------------------------------------------------------- */

Does that comment really mean that the non-NULL return value might
become invalid as soon as the lock is released?

Which would mean that you've removed the wrong unlock!

        David

-- 
David Laight: david%l8s.co.uk@localhost