linux-kernel - Re: [PATCH] nextfd(2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACVxJT_RRfW7HknkbA4+41L9hNMBHZNezKs1ifbv_qFx5eB0-w@mail.gmail.com>
Date:	Thu, 12 Apr 2012 13:54:25 +0300
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	akpm@...ux-foundation.org, viro@...iv.linux.org.uk,
	torvalds@...ux-foundation.org, drepper@...il.com,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] nextfd(2)

On Sat, Apr 7, 2012 at 12:02 AM, H. Peter Anvin <hpa@...or.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/