[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACVxJT-YmJQcp9PPhA1cx3rzUF1onzg-AzpC88L+QXz9xgYGtQ@mail.gmail.com>
Date: Wed, 25 Oct 2017 14:45:31 +0200
From: Alexey Dobriyan <adobriyan@...il.com>
To: Pavel Machek <pavel@....cz>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-api@...r.kernel.org, rdunlap@...radead.org,
tglx@...utronix.de, tixxdz@...il.com, gladkov.alexey@...il.com,
Aliaksandr Patseyenak <Aliaksandr_Patseyenak1@...m.com>
Subject: Re: [PATCH 1/2 v2] fdmap(2)
On 10/23/17, Pavel Machek <pavel@....cz> wrote:
> Binary fdmap looks... quite ugly to me. But close_all(from, to)
> syscall kindof makes sense to me... and is not that ugly.
>
> Given that openbsd has something similar... perhaps we can take that?
closefrom() can be implemented on top of fdmap().
fdmap as is is useful for other purposes.
> Except during startup, application should have good idea what fds it
> has open, so maybe that's enough?
Powered by blists - more mailing lists