From owner-cvs-all@FreeBSD.ORG Wed Mar 26 15:23:20 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ACD937B404; Wed, 26 Mar 2003 15:23:20 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B75743F75; Wed, 26 Mar 2003 15:23:19 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.8/8.12.8) with SMTP id h2QNNEjK032829; Wed, 26 Mar 2003 18:23:14 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 26 Mar 2003 18:23:13 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kris Kennaway In-Reply-To: <20030326225019.GA11327@rot13.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-23.2 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REPLY_WITH_QUOTES,USER_AGENT_PINE version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/nfsclient nfs_lock.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 23:23:22 -0000 On Wed, 26 Mar 2003, Kris Kennaway wrote: > Thanks, this sounds like it may fix non-blocking calls to open() on a > NFS file, which would previously block. Well, it depends whether the open() had flags like O_SHLOCK or O_EXLOCK set. This will only affect cases where advisory locking primitives were used by userspace applications, resulting in a call into the NFS locking code. Interestingly, this case would previously timeout with: foo: Resource temporarily unavailable on -CURRENT, but not -STABLE, due to a deadlock work-around in the fifo code. Only when the work-around was removed did this case pop up--before the diskless boot would pause occasionally waiting for fifos to time out, but then continue. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories