Date: Sun, 07 Feb 2016 21:22:29 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 206927] Bad semaphore return code on collision Message-ID: <bug-206927-8-gtilHA2Jap@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206927-8@https.bugs.freebsd.org/bugzilla/> References: <bug-206927-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206927 Jilles Tjoelker <jilles@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |jilles@FreeBSD.org Status|New |In Progress CC| |jilles@FreeBSD.org --- Comment #1 from Jilles Tjoelker <jilles@FreeBSD.org> --- The additional [EINVAL] condition is missing from the semget(2) man page; I will add it. Although POSIX leaves the detection order of errors undefined (XSH 2.3 Error Numbers), detecting [EINVAL] before [EEXIST] is clearly inconvenient for applications. The inconvenient order has been in place for years, but it is easy to change. You could request the Austin Group to make this unambiguous (e.g., restrict part of the [EINVAL] error to not occur if ((semflg&IPC_CREAT)&&(segflg&IPC_EXCL)) is non-zero). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206927-8-gtilHA2Jap>