This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Re: [PATCH 3/6] Reinstantiate fd range check if and only if defined _STRICT_FD_SIZE_CHECK=1
- From: KOSAKI Motohiro <kosaki dot motohiro at gmail dot com>
- To: Arjan van de Ven <arjan at linux dot intel dot com>
- Cc: chrubis at suse dot cz, Florian Weimer <fweimer at redhat dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Wed, 3 Apr 2013 23:49:51 -0400
- Subject: Re: Re: [PATCH 3/6] Reinstantiate fd range check if and only if defined _STRICT_FD_SIZE_CHECK=1
- References: <20130403094821 dot GA1545 at rei> <515C4C24 dot 2070703 at linux dot intel dot com>
> ... and that is done deliberately accepting that it is breaking some broken
> code.
> if you don't want to deal with it, then don't enable it!
> (and if it's for one package only, it's up to the people who added it to
> cflags, to
> unadd it inside their specfile)
Detecting breaking code is a nice to have. But not to break innocent
applications
is a must to have. And it's not one package only, as previous
discussion pointed out.
Adding new FORTIFY option is not ideal, but best.