This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: What *is* the API for sched_getaffinity? Should sched_getaffinity always succeed when using cpu_set_t?
- From: Rich Felker <dalias at aerifal dot cx>
- To: Andreas Jaeger <aj at suse dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 15 Jul 2013 20:33:04 -0400
- Subject: Re: What *is* the API for sched_getaffinity? Should sched_getaffinity always succeed when using cpu_set_t?
- References: <51E42BFE dot 7000301 at redhat dot com> <51E43D95 dot 8050509 at suse dot com>
On Mon, Jul 15, 2013 at 08:21:09PM +0200, Andreas Jaeger wrote:
> There's another solution: Increasing __CPU_SETSIZE to a larger value.
>
> This is what a previous SUSE maintainer did for our glibc (changing to
> 4096). Unfortunately that issue seems to not have been discussed here;(
That does not fix the problem, it just changes the point at which the
problem occurs. It also breaks the ABI badly, in ways that would be
dangerous buffer overflows if you didn't use a new symbol version (and
even then, the danger remains for certain usages).
Rich