> >>    On the other hand, keeping it as uio_proc, would require us to call
> >>    proc_representative_lwp(uio->uio_proc) in a bunch of places; not very
> >>    attractive either.
> >
> >where is "a bunch of places" for example?
> >using uio_proc for other than address space is evil, IMO.
> >if proc (or lwp, or ucred, etc) is really necessary,
> >it should be passed as another argument.  (or curlwp, where appropriate.)
> 
> Not many places. The most common users are socket/io and nfs.
> 
> christos

some of them were changed from curproc recently as a part of
kill-curproc-blindly efforts, which IMO should have been done differently.

YAMAMOTO Takashi