Messages in this thread | | | Date | Thu, 12 Apr 2012 13:54:25 +0300 | Subject | Re: [PATCH] nextfd(2) | From | Alexey Dobriyan <> |
| |
On Sat, Apr 7, 2012 at 12:02 AM, H. Peter Anvin <hpa@zytor.com> wrote: > On 04/06/2012 01:16 PM, Alexey Dobriyan wrote: >> >> closefrom(3) written via nextfd(2) loop is reliable and doesn't fail. >> closefrom(3) written via /proc/self/fd is reliable and can fail (including ENOMEM). >> closefrom(3) written via close(fd++) is unreliable. >> > > I call shenanigans on this. There is no reason to ENOMEM on the second > written using the fdwalk() implementation I already posted, for example.
open("/proc/self/fd") can fail with ENOMEM. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |