Subject: Re: wrap up of pipe(2)
To: Bill Sommerfeld <firstname.lastname@example.org>
From: Andrew Brown <email@example.com>
Date: 10/03/2001 16:44:55
>When I get a chance (and if someone doesn't beat me to it), I'd be
>inclined to make a pass through the section 2 manual pages to improve
would this include adding all the possible errno values to all the
syscall man pages? ioctl, to pick a well known (to me) example, is
documented to possibly "return" an errno of:
but can also "return":
and, of course, EFAULT. all that, and i'm not even done reading the
ioctl code path.
> - document in intro(2) and elsewhere that, on some architectures, any
>syscall which takes arguments can conceivably return EFAULT if the
>copyin() of the arguments fails. (In practice, you'll need a
>"special" syscall stub to trigger this).
...and also EFAULT on copyout(), just to be pedantic. :)
|-----< "CODE WARRIOR" >-----|
firstname.lastname@example.org * "ah! i see you have the internet
email@example.com (Andrew Brown) that goes *ping*!"
firstname.lastname@example.org * "information is power -- share the wealth."