From owner-freebsd-stable Sun Jul 22 17: 7: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C62C137B407 for ; Sun, 22 Jul 2001 17:06:58 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Jul 2001 01:06:58 +0100 (BST) To: freebsd-stable@freebsd.org Subject: API change requiring filesystem module recompilation Date: Mon, 23 Jul 2001 01:06:58 +0100 From: Ian Dowse Message-ID: <200107230106.aa13050@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I would like to bring into -stable a small API change that will unfortunately require the recompilation of any filesystem modules. This change fixes some bugs relating to forcibly unmounting certain filesystems while there are extra references held on the filesystem root vnode. It has been in -current for 2 months. The kernel function vflush() is used by all filesystems at unmount time to flush out any active vnodes belonging to the filesystem being unmounted. It is also the function that decides if a filesystem is busy when you try to unmount it. The API for this function made it hard for filesystems that hold extra references on the filesystem root vnode; they had to repeat a lot of what vflush() does themselves, and as a result many got it wrong. The API modification allows vflush() to do all the work itself so that it is easy for filesystems to flush all their vnodes. This is a non-critical bugfix, but it will also simplify the porting of any new filesystems from -current to -stable. Are there any good reasons, such as 3rd party filesystem modules in use that would make recompilation of filesystem modules a problem? Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message