> due to a copyout glitch.
> 
> It seems that copyout() can fail even when passed a zero length, if the
> userland pointer is pointing into kernel space.  At least on the sparc.

i think it's correct behavior.
 
> Is this as it should be?  If so, I'd recommend that copyout(9) be much
> more noisy about it, as traditionally bcopy-style routines don't care
> what their pointers are when they aren't copying anything.  (And if
> not, at least one port has a bug to fix. :-)
> 
> /~\ The ASCII				der Mouse
> \ / Ribbon Campaign
>  X  Against HTML	       mouse@rodents.montreal.qc.ca
> / \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>