From owner-cvs-all Fri Sep 25 11:46:09 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18514 for cvs-all-outgoing; Fri, 25 Sep 1998 11:46:09 -0700 (PDT) (envelope-from owner-cvs-all) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18429 for ; Fri, 25 Sep 1998 11:45:55 -0700 (PDT) (envelope-from dillon@backplane.com) Received: (dillon@localhost) by apollo.backplane.com (8.9.1/8.6.5) id LAA26836; Fri, 25 Sep 1998 11:45:46 -0700 (PDT) Date: Fri, 25 Sep 1998 11:45:46 -0700 (PDT) From: Matthew Dillon Message-Id: <199809251845.LAA26836@apollo.backplane.com> To: committers@FreeBSD.ORG Subject: VM fix for write()/mmap() corruption PR going in later today Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It looks like the fix is working. I'm hoping to get confirmation from another party later today and then intend to commit it. The patch will consist of clearing B_RELBUF in brelse() if B_DELWRI is set, just prior to the VMIO buffer rundown, basically: /* * Clear B_RELBUF if B_DELWRI is set. We absolutely * cannot call vfs_vmio_release() if B_DELWRI is set or we may * lose data writes. */ if (bp->b_flags & B_DELWRI) bp->b_flags &= ~B_RELBUF; The patch will be commited into -current later today. I would also like to commit the patch to -stable so it gets into 2.2.8 as there have also been reports of the corruption occuring on -stable systems. I have also tested it on one of our other -stable based news machines and it seems to do no harm. Does anyone have any objections to my commiting the patch into -stable as well? -Matt