From owner-cvs-all  Thu Jan 21 22:05:11 1999
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA24408
          for cvs-all-outgoing; Thu, 21 Jan 1999 22:05:11 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24402;
          Thu, 21 Jan 1999 22:05:08 -0800 (PST)
          (envelope-from dillon@FreeBSD.org)
From: Matt Dillon <dillon@FreeBSD.ORG>
Received: (from dillon@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id WAA00152;
	Thu, 21 Jan 1999 22:05:09 -0800 (PST)
Date: Thu, 21 Jan 1999 22:05:09 -0800 (PST)
Message-Id: <199901220605.WAA00152@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: cvs commit: src/sys/vm vm_pageout.c
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

dillon      1999/01/21 22:05:09 PST

  Modified files:        (Branch: RELENG_3)
    sys/vm               vm_pageout.c 
  Log:
      Backport from -4.x.
  
      We cannot call vm_object_collapse() here because it could block and
      we are not holding any locks on our vm_object or vm_page_t.  If it
      were to block, the system might shred the objects that we assume remain
      consistent.
  
      John Dyson is not 100% sure that VM objects are collapsed properly
      in all cases ( i.e. 'garbage collected' ), and this code was originally
      put in to solve a related problem.  For now we assume that VM objects
      are collapsed properly.  If it turns out they are not, we will fix
      that problem.  The problem this patch fixes, however, could cause a crash
      and must be fixed now.
  
  Revision  Changes    Path
  1.129.2.1 +7 -2      src/sys/vm/vm_pageout.c

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