Date: Sun, 3 Feb 2013 20:52:32 -0500 From: Eitan Adler <lists@eitanadler.com> To: Giorgos Keramidas <keramida@freebsd.org>, Jilles Tjoelker <jilles@stack.nl> Cc: freebsd-bugs@freebsd.org Subject: Re: kern/175674: sem_open() should use O_EXLOCK with open() instead of a separate flock() call Message-ID: <CAF6rxgmmftGBtMm4fOoExLgRz3RDd=omEP4zkW4wtLuq=T-Q6w@mail.gmail.com> In-Reply-To: <201302032100.r13L01PG044439@freefall.freebsd.org> References: <201302032100.r13L01PG044439@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3 February 2013 16:00, Giorgos Keramidas <keramida@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgmmftGBtMm4fOoExLgRz3RDd=omEP4zkW4wtLuq=T-Q6w>