From owner-freebsd-audit  Mon Apr 16  5:54:25 2001
Delivered-To: freebsd-audit@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by hub.freebsd.org (Postfix) with ESMTP
	id C6E0137B42C; Mon, 16 Apr 2001 05:54:20 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f3GCsFU02210;
	Mon, 16 Apr 2001 14:54:16 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: arch@freebsd.org, audit@freebsd.org
Subject: [PATCH] Axing VOP_BWRITE
From: Poul-Henning Kamp <phk@freebsd.org>
Date: Mon, 16 Apr 2001 14:54:15 +0200
Message-ID: <2208.987425655@critter>
Sender: owner-freebsd-audit@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I have made a patch which axes VOP_BWRITE:

	http://phk.freebsd.dk/patch/buf_write.patch

20010416        buf_write.patch

        This patch removes the VOP_BWRITE() vector.

        VOP_BWRITE() was a hack which made it possible for NFS client
        side to use struct buf with non-bio backing.

        This patch takes a more general approach and adds a bp->b_op
        vector where more methods can be added.

        The success of this patch depends on bp->b_op being initialized
        all relevant places for some value of "relevant" which is not
        easy to determine.

        As a followup to this patch, all uses of
                bwrite(bp)
        should be changed to
                BUF_BWRITE(bp)


--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-audit" in the body of the message