This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH v3] getrandom system call wrapper [BZ #17252]
- From: Torvald Riegel <triegel at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 09 Sep 2016 16:21:45 +0200
- Subject: Re: [PATCH v3] getrandom system call wrapper [BZ #17252]
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com>
On Thu, 2016-09-08 at 13:44 +0200, Florian Weimer wrote:
> I have made the system call wrapper a cancellation point. (If we
> implement the simpler getentropy interface, it would not be a
> cancellation point.)
Why did you do that? Even though the system call is new, and thus can't
have been used in existing code directly, making it a cancellation point
will make all callers cancellation points too. Therefore, for example,
we couldn't use it in the implementation of any POSIX functions (that
are not cancellation points) in glibc without having to disable and
restore the cancellation state around it every time.
It might be even more convenient to have one wrapper that is a
cancellation point and one that is not.
Can't we just let cancellation rot in its corner?