Date: Wed, 26 Mar 2003 18:23:13 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: Kris Kennaway <kris@obsecurity.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/nfsclient nfs_lock.c Message-ID: <Pine.NEB.3.96L.1030326182038.18064c-100000@fledge.watson.org> In-Reply-To: <20030326225019.GA11327@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030326182038.18064c-100000>