On Tue, Sep 20, 2011 at 09:47:45AM +0200, Mark Kettenis wrote:
> > Date: Tue, 20 Sep 2011 01:41:35 +0300
> > From: Paul Irofti
> >
> > Linux keeps surprising me everytime!
> >
> > This time its their pipe2 system call which adds flags to the pipe call.
> > Its the unix-ish way apparently to turn
> Date: Tue, 20 Sep 2011 01:41:35 +0300
> From: Paul Irofti
>
> Linux keeps surprising me everytime!
>
> This time its their pipe2 system call which adds flags to the pipe call.
> Its the unix-ish way apparently to turn pipes into files on a kernel
> filesystem, or so they claim.
>
> Anywho, th
On Mon, Sep 19, 2011 at 4:22 PM, Joerg Sonnenberger
wrote:
> No, the idea is to make it possible to set O_CLOEXEC atomically. Of
> course, the pipe2 system call as implemented in Linux is kind of messed
> up, since the flag attribute applies to both sides of the pipe.
If you need O_CLOEXEC, you w
On Tue, Sep 20, 2011 at 01:41:35AM +0300, Paul Irofti wrote:
> This time its their pipe2 system call which adds flags to the pipe call.
> Its the unix-ish way apparently to turn pipes into files on a kernel
> filesystem, or so they claim.
No, the idea is to make it possible to set O_CLOEXEC atomic
Linux keeps surprising me everytime!
This time its their pipe2 system call which adds flags to the pipe call.
Its the unix-ish way apparently to turn pipes into files on a kernel
filesystem, or so they claim.
Anywho, this fixes glibc pipe2 system calls by wrapping against the
regular pipe systemc
