From owner-freebsd-bugs@FreeBSD.ORG Mon Feb 4 02:40:01 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A6F09E44 for ; Mon, 4 Feb 2013 02:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 9786D853 for ; Mon, 4 Feb 2013 02:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r142e1hD029471 for ; Mon, 4 Feb 2013 02:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r142e1Bd029466; Mon, 4 Feb 2013 02:40:01 GMT (envelope-from gnats) Date: Mon, 4 Feb 2013 02:40:01 GMT Message-Id: <201302040240.r142e1Bd029466@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Eitan Adler Subject: Re: kern/175674: sem_open() should use O_EXLOCK with open() instead of a separate flock() call X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Eitan Adler List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 02:40:01 -0000 The following reply was made to PR kern/175674; it has been noted by GNATS. From: Eitan Adler To: bug-followup 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 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 , Jilles Tjoelker Cc: freebsd-bugs@freebsd.org On 3 February 2013 16:00, Giorgos Keramidas 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