On Mon, 24 Aug 1998, Lennart Augustsson wrote:

> It used to be the case (pre-UVM) that if you called uiomove() to
> copy from kernel to kernel space it used memcpy().  This meant
> that you could call it from an interrupt context and just set
> the uio_procp field to 0.  I was a bit lazy so I used it that way,
> but I'm rewriting that code now.
Well does this raise a question over the use of kcopy() or uiomove() from
interrupt contexts ?
There are points where curproc and curpcb may be NULL and thus during
these periods kcopy() cannot be used. If kcopy() is being indirectly
called from an interrupt context this this would require that interrupts
are always blocked if curproc/curpcb is zero.
This means that perhaps there is a point where curpcb is zero but
interrupts have not been disabled when they should have.

Cheers,
				Mark