Re: kern/59498: Add missing POSIX O_CLOFORK flag

["Ricardo Branco via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR kern/59498; it has been noted by GNATS.

From: Ricardo Branco <rbranco%suse.de@localhost>
To: gnats-bugs%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/59498: Add missing POSIX O_CLOFORK flag
Date: Tue, 1 Jul 2025 19:20:47 +0200

 On 7/1/25 7:15 PM, Robert Elz via gnats wrote:
 > The following reply was made to PR kern/59498; it has been noted by GNATS.
 >
 > From: Robert Elz <kre%munnari.OZ.AU@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: kern/59498: Add missing POSIX O_CLOFORK flag
 > Date: Wed, 02 Jul 2025 00:13:07 +0700
 >
 >       Date:        Tue,  1 Jul 2025 16:05:00 +0000 (UTC)
 >       From:        rbranco%suse.de@localhost
 >       Message-ID:  <20250701160500.760D61A9242%mollari.NetBSD.org@localhost>
 >   
 >   Have you investigated how many (if any, I haven't looked) of
 >   the applications in NetBSD simply assume get fcntl(fd, F_GETFD)
 >   returning non-zero means that close-on-exec is set ?
 >   
 >   That's what I always considered the most difficult part of
 >   implementing O_CLOFORK -- the alteration of this fairly long
 >   held assumption.
 >   
 >   kre
 >   
 
 In this implementation, O_CLOFORK is cleared on exec, so
 this point is moot for applications.
 
 Library code needs minor fixing, though.  That can be done
 and should be done.
 
 Best,
 Ricardo.