From owner-cvs-sys  Fri Mar  7 01:51:48 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA01025
          for cvs-sys-outgoing; Fri, 7 Mar 1997 01:51:48 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA01017;
          Fri, 7 Mar 1997 01:51:40 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id UAA10031; Fri, 7 Mar 1997 20:42:40 +1100
Date: Fri, 7 Mar 1997 20:42:40 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703070942.UAA10031@godzilla.zeta.org.au>
To: cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org,
        cvs-sys@freefall.freebsd.org, joerg@freefall.freebsd.org
Subject: Re: cvs commit:  src/sys/ufs/mfs mfs_vfsops.c
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>  Branch:      sys/ufs/mfs  RELENG_2_2
>  Modified:    sys/ufs/mfs  mfs_vfsops.c
>  Log:
>  YAMFC (rev 1.27: supply the mount point when getting a vnode)

I don't trust this change.  Maybe something uses vp->v_mount == NULL
to give special behaviour for mfs.

Looking for tests of vp->v_mount, I found that cluster_write() begins
with a usless test of vp->v_mount.  The next line indirects through
vp->v_mount unconditionally.

Bruce