Found 12 matching messages (0.079 seconds). Page 1 of 1.
This version of the patch hopefully integrates all of the requested ... socket() and socketpair(). Seems cleaner. I tried to write the paccept() ... 0); if (s < 0) { puts ("socket(SOCK_CLOEXEC) failed"); status = 1; } else ...
linux-kernel - Ulrich Drepper - Apr 26 2008 - 18:24
This version of the patch hopefully integrates all of the requested ... socket() and socketpair(). Seems cleaner. I tried to write the paccept() ... 0); if (s < 0) { puts ("socket(SOCK_CLOEXEC) failed"); status = 1; } else ...
linux-netdev - Ulrich Drepper - Apr 26 2008 - 18:24
... do is to write > > > fd = socket(PF_INET, SOCK_STREAM|SOCK_CLOEXEC, 0); > if ... I didn't read your patches closely > > enough). However, the rationale ... dup3() -- all use O_CLOEXEC > > socketpair(), socket(), paccept -- all use SOCK_CLOEXEC > > pipe2 ...
linux-kernel - Michael Kerrisk - Apr 28 2008 - 11:29
... do is to write > > > fd = socket(PF_INET, SOCK_STREAM|SOCK_CLOEXEC, 0); > if ... I didn't read your patches closely > > enough). However, the rationale ... dup3() -- all use O_CLOEXEC > > socketpair(), socket(), paccept -- all use SOCK_CLOEXEC > > pipe2 ...
linux-netdev - Michael Kerrisk - Apr 28 2008 - 11:29
... to have new syscalls for socket() and socketpair(). I understand your reasoning for ... and I didn't read your patches closely enough). However, the rationale for ... dup3() -- all use O_CLOEXEC socketpair(), socket(), paccept -- all use SOCK_CLOEXEC pipe2() ...
linux-netdev - Michael Kerrisk - Apr 28 2008 - 10:51
... to have new syscalls for socket() and socketpair(). I understand your reasoning for ... and I didn't read your patches closely enough). However, the rationale for ... dup3() -- all use O_CLOEXEC socketpair(), socket(), paccept -- all use SOCK_CLOEXEC pipe2() ...
linux-kernel - Michael Kerrisk - Apr 28 2008 - 10:51
... to do is to write fd = socket(PF_INET, SOCK_STREAM|SOCK_CLOEXEC, 0); if ( ... I didn't read your patches closely > enough). However, the rationale ... dup3() -- all use O_CLOEXEC > socketpair(), socket(), paccept -- all use SOCK_CLOEXEC > pipe2() ...
linux-kernel - Ulrich Drepper - Apr 28 2008 - 11:13
... to do is to write fd = socket(PF_INET, SOCK_STREAM|SOCK_CLOEXEC, 0); if ( ... I didn't read your patches closely > enough). However, the rationale ... dup3() -- all use O_CLOEXEC > socketpair(), socket(), paccept -- all use SOCK_CLOEXEC > pipe2() ...
linux-netdev - Ulrich Drepper - Apr 28 2008 - 11:13
... com> wrote: > This version of the patch hopefully integrates all of the requested ... the new accept interface is now paccept() which adds the flag > parameter as ... as the ORed flags for > socket() and socketpair(). Seems cleaner. Ulrich, This is ...
linux-netdev - Michael Kerrisk - Apr 28 2008 - 05:52
... com> wrote: > This version of the patch hopefully integrates all of the requested ... the new accept interface is now paccept() which adds the flag > parameter as ... as the ORed flags for > socket() and socketpair(). Seems cleaner. Ulrich, This is ...
linux-kernel - Michael Kerrisk - Apr 28 2008 - 05:52
... problem here. > then *please* let's go the hwole way cleanly, and have new syscalls > also for socketpair() and socket(), and make all of the new syscalls > use the same flags. Hell, no, that's worse than ...
linux-netdev - Ulrich Drepper - Apr 28 2008 - 10:13
... problem here. > then *please* let's go the hwole way cleanly, and have new syscalls > also for socketpair() and socket(), and make all of the new syscalls > use the same flags. Hell, no, that's worse than ...
linux-kernel - Ulrich Drepper - Apr 28 2008 - 10:13