Date: Fri, 27 Jan 2006 12:24:30 -0500 (EST) From: Garrett Wollman <wollman@khavrinen.csail.mit.edu> To: glebius@freebsd.org Cc: arch@freebsd.org Subject: Re: fix return code for pipe(2) syscall Message-ID: <200601271724.k0RHOUat034301@khavrinen.csail.mit.edu> In-Reply-To: <20060127093602.GO83922@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20060127093602.GO83922@cell.sick.ru> you write: >Yes, according to SUSv3 the only errors from pipe(2) are ENFILE >and EMFILE. POSIX does not define an exhaustive enumeration of error conditions. *Any* error return is permissible, provided only that *for those conditions noted in the ERRORS section* the code identified for that condition is returned. It is perfectly permissible for every system call to fail with [ENOTADUCK] unless the first five bytes of the caller's address space contain the word "quack". -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601271724.k0RHOUat034301>