Date: Tue, 31 Oct 1995 06:21:27 -0800 From: David Greenman <davidg@Root.COM> To: Terry Lambert <terry@lambert.org> Cc: current@freebsd.org Subject: Re: *MORE* FS problems, please fix! Message-ID: <199510311421.GAA09530@corbin.Root.COM> In-Reply-To: Your message of "Mon, 30 Oct 95 13:39:09 MST." <199510302039.NAA06584@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> The locking subsystem is *incorrectly* implementing locking via a > call to vn_* from the file system specific lock code. > > > The design says that the FS specific lock code is, in fact, advisory. Advisory locks *are* advisory. The advisory locking is implemented via VOP_ADVLOCK() in the appropriate system calls. Is this another case where you completely misunderstand, at the most fundamental level, how the code works? If you're looking at VOP_LOCK/VOP_UNLOCK and thinking that these have something to do with file locking, look again, they don't. -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510311421.GAA09530>