Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Nov 2011 08:42:56 GMT
From:      Yui NARUSE <naruse@airemix.jp>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   kern/162374: posix_openpt wrongly removed O_CLOEXEC
Message-ID:  <201111080842.pA88guL0015678@red.freebsd.org>
Resent-Message-ID: <201111080850.pA88o1XT018354@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         162374
>Category:       kern
>Synopsis:       posix_openpt wrongly removed O_CLOEXEC
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 08 08:50:00 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Yui NARUSE
>Release:        FreeBSD 9.0-RC1
>Organization:
>Environment:
FreeBSD windy.airemix.net 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 18 18:51:43 UTC 2011     root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
FreeBSD 8 undocumentedly supported O_CLOEXEC flag for posix_openpt.
But FreeBSD 9 removed it because it is not in SuSv4.
http://freebsd.1045724.n5.nabble.com/O-CLOEXEC-td4263370.html

However next SuS will add O_CLOEXEC for posix_openpt just as FreeBSD 8.2 did.
http://austingroupbugs.net/view.php?id=411

This means, FreeBSD 8.2 and future FreeBSD supports O_CLOEXEC for posix_openpt, but FreeBSD 9.0 doesn't. It is very confusing.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201111080842.pA88guL0015678>