This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Assume that dup3 is available
- From: Florian Weimer <fweimer at redhat dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, libc-alpha at sourceware dot org
- Date: Mon, 17 Apr 2017 22:11:25 +0200
- Subject: Re: [PATCH] Assume that dup3 is available
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=fweimer at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 962B280E4A
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 962B280E4A
- References: <20170413192548.BF5A040EBCF62@oldenburg.str.redhat.com> <91373be4-3688-abf4-628a-9a510e4c2678@linaro.org>
On 04/17/2017 08:16 PM, Adhemerval Zanella wrote:
Shouldn't we check the result of __dup3 and act accordingly in this situation
(basically EINTR and EMFILE)?
Yes, but that's an existing bug in the code. I would like to keep this
change the bug fix separate. I filed bug 21393 for the missing error check.
Thanks,
Florian