This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: [PATCH v4 0/5] fix wrong program abort on __FD_ELT
- From: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>, "libc-ports at sourceware dot org" <libc-ports at sourceware dot org>
- Date: Wed, 1 May 2013 01:31:15 -0400
- Subject: Re: [PATCH v4 0/5] fix wrong program abort on __FD_ELT
- References: <1365900451-19026-1-git-send-email-kosaki dot motohiro at gmail dot com> <51808721 dot 5090507 at redhat dot com>
On Tue, Apr 30, 2013 at 11:08 PM, Carlos O'Donell <carlos@redhat.com> wrote:
> On 04/13/2013 08:47 PM, KOSAKI Motohiro wrote:
>> Changes from v3 to v4
>> - remove _STRICT_FD_SIZE_CHECK ifdef.
>> - instead, always check buffersize. requested from Florian Weimer.
>
> Do we want to update manual/llio.texi to describe those macros
> that can work with heap allocated fd sets?
>
> These macros are being clearly used in Linux and BSD to operate
> on heap allocated sets, and the glibc versions of some of these
> macros do support those uses.
The manual already explains this case. I guess GNU/Hurd also support
the same extension.
@comment sys/types.h
@comment BSD
@deftypevr Macro int FD_SETSIZE
The value of this macro is the maximum number of file descriptors that a
@code{fd_set} object can hold information about. On systems with a
fixed maximum number, @code{FD_SETSIZE} is at least that number. On
some systems, including GNU, there is no absolute limit on the number of
descriptors open, but this macro still has a constant value which
controls the number of bits in an @code{fd_set}; if you get a file
descriptor with a value as high as @code{FD_SETSIZE}, you cannot put
that descriptor into an @code{fd_set}.
@end deftypevr