Steve Simon once said:
> The difference comes from the fact that sleep is deep inside its
> stack/errlab hierarchy when it receives a note. This causes it
> to jump to the notify function (still in the users context),
> the notify function then calls back into the kernel (noted()).
>
> this is wh
> Waserror increments up->nerrlab before setting up
> the next label on the error stack which means the
> poperror in question returns it to zero.
Yep, I get this part, and for nearly all syscalls its straightforward,
fork() is different (I was stumpped by that a few months ago), and it seems
note
Waserror increments up->nerrlab before setting up
the next label on the error stack which means the
poperror in question returns it to zero.
Anthony
