From owner-cvs-all  Thu Nov  8 19:42:33 2001
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 85B9837B416; Thu,  8 Nov 2001 19:42:28 -0800 (PST)
Received: (from dillon@localhost)
	by freefall.freebsd.org (8.11.4/8.11.4) id fA93gSV34824;
	Thu, 8 Nov 2001 19:42:28 -0800 (PST)
	(envelope-from dillon)
Message-Id: <200111090342.fA93gSV34824@freefall.freebsd.org>
From: Matt Dillon <dillon@FreeBSD.org>
Date: Thu, 8 Nov 2001 19:42:28 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/dev/vn vn.c
X-FreeBSD-CVS-Branch: RELENG_4
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

dillon      2001/11/08 19:42:28 PST

  Modified files:        (Branch: RELENG_4)
    sys/dev/vn           vn.c 
  Log:
  Fix a long standing (since '94) error in VN related to file-backed VN
  devices.  The VOP_ISLOCKED() call was completely bogus and could cause
  the VN device to issue VOP_READ() and VOP_WRITE() calls without obtaining
  the vnode lock if another process (e.g. like the buf_daemon or syncer)
  was holding the lock.  This could potentially result in a corrupt filesystem.
  
  (MD in -current already does the right thing).
  
  Revision   Changes    Path
  1.105.2.3  +5 -12     src/sys/dev/vn/vn.c

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