From owner-cvs-all Sat Jul 6 0:16:44 2002 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 E11DC37B400; Sat, 6 Jul 2002 00:16:41 -0700 (PDT) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A23E43E31; Sat, 6 Jul 2002 00:16:41 -0700 (PDT) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g667GeK49968; Sat, 6 Jul 2002 03:16:40 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sat, 6 Jul 2002 03:16:40 -0400 (EDT) From: Jeff Roberson To: Jeff Roberson Cc: cvs-committers@FreeBSD.org, Subject: Re: cvs commit: src/sys/sys vnode.h src/sys/kern vfs_subr.c In-Reply-To: <200207060521.g665LDPF084921@freefall.freebsd.org> Message-ID: <20020706031458.U25604-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 5 Jul 2002, Jeff Roberson wrote: > > VOP_STRATEGY requires only that the buf is locked UNLESS the block numbers need > to be translated. There may be other reasons, but as long as the underlying > layer uses a VOP to perform the operations they will be caught later. > Can anyone elaborate on buf locking? It looks like the cluster_* functions never lock the buf. Maybe I'm missing the point of the buf locking, or maybe this stuff really is unsafe. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message