From owner-freebsd-current Sat Nov 6 11:14:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id DAF1414BDC; Sat, 6 Nov 1999 11:14:18 -0800 (PST) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id WAA24069; Sat, 6 Nov 1999 22:13:44 +0300 (MSK) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id WAA02732; Sat, 6 Nov 1999 22:21:03 +0300 (MSK) (envelope-from dima@tejblum.pp.ru) Message-Id: <199911061921.WAA02732@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: David Malone Cc: Ollivier Robert , "FreeBSD Current Users' list" , green@FreeBSD.ORG From: Dmitrij Tejblum Subject: Re: Serious locking problem in CURRENT In-reply-to: Your message of "Sat, 06 Nov 1999 13:45:48 GMT." <19991106134548.A2921@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Nov 1999 22:21:03 +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > A child process seems to be able to let go of a parent's lock on > 4.0 by closing a file discriptor, the same doesn't seem to be true > on 3.3. So, apparently, it was broken in rev. 1.68 of kern_descript.c. (Another example that comments (in closef() in this case) serve no purpose :-/). BTW, I have another little concern with that commit: It make possible for last close() of a file descriptor to return 0 instead of the error from VOP_CLOSE(), and the error from VOP_CLOSE() to be ignored. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message