Re: [PATCH] cleanup paccept

[Michael Kerrisk]

>> The actual patch which is in the kernel is different from
>> the patch in the mail: only the signal mask handling has been disabled.
>> This is why this is only a cleanup patch.
>
> And that does not explain to the world at large what this
> to-be-enabled system call does, or why it's needed.

And one further point: what is the userspace interface going to look
like for this system call?

Are we to see a repeat of the unsafe userspace implementation of
pselect() that was present in glibc before the kernel finally added a
pselect() system call?

In other words: is the userspace interface for accept4() going to be
the thinnest of wrappers, or will glibc add an unsafe
paccept()-with-signal-mask in userspace?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/