kern/175674: sem_open() should use O_EXLOCK with open() instead of a separate flock() call
Eitan Adler
lists at eitanadler.com
Mon Feb 4 02:40:01 UTC 2013
The following reply was made to PR kern/175674; it has been noted by GNATS.
From: Eitan Adler <lists at eitanadler.com>
To: bug-followup <bug-followup at freebsd.org>
Cc:
Subject: Re: kern/175674: sem_open() should use O_EXLOCK with open() instead
of a separate flock() call
Date: Sun, 3 Feb 2013 21:30:28 -0500
---------- Forwarded message ----------
From: Eitan Adler <lists at eitanadler.com>
Date: 3 February 2013 20:52
Subject: Re: kern/175674: sem_open() should use O_EXLOCK with open()
instead of a separate flock() call
To: Giorgos Keramidas <keramida at freebsd.org>, Jilles Tjoelker <jilles at stack.nl>
Cc: freebsd-bugs at freebsd.org
On 3 February 2013 16:00, Giorgos Keramidas <keramida at freebsd.org> wrote:
> The following reply was made to PR kern/175674; it has been noted by GNATS.
> > The best way to fix this is in kern_openat() in the kernel but this
> > might cause compatibility issues.
>
> Not sure if there would be serious compatibility problems if open() would
> automatically restart instead of returning EINTR. It definitely seems a rather
> intrusive change though.
I can not see major application breakage should open(3) be changed.
That said, I am confused by jilles' comment:
http://pubs.opengroup.org/onlinepubs/000095399/functions/open.html
open(3) is permitted to return EINTR.
--
Eitan Adler
--
Eitan Adler
More information about the freebsd-bugs
mailing list