From owner-cvs-sys  Mon Dec  8 21:05:56 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id VAA28096
          for cvs-sys-outgoing; Mon, 8 Dec 1997 21:05:56 -0800 (PST)
          (envelope-from owner-cvs-sys)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA28039;
          Mon, 8 Dec 1997 21:05:21 -0800 (PST)
          (envelope-from sef@FreeBSD.org)
From: Sean Eric Fagan <sef@FreeBSD.ORG>
Received: (from sef@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id VAA25960;
	Mon, 8 Dec 1997 21:03:43 -0800 (PST)
Date: Mon, 8 Dec 1997 21:03:43 -0800 (PST)
Message-Id: <199712090503.VAA25960@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG
Subject: cvs commit: src/sys/miscfs/procfs procfs_subr.c
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

sef         1997/12/08 21:03:43 PST

  Modified files:
    sys/miscfs/procfs    procfs_subr.c 
  Log:
  Code to prevent a panic caused by procfs_exit().  Note that i don't know
  what is teh root cause -- but, sometimes, a procfs vnode in pfshead is
  apparantly corrupt (or a UFS vnode instead).  Without this patch, I can
  get it to panic by doing (in csh)
  
  	while (1)
  		ps auxwww
  	end
  
  and it will panic when the PID's wrap.  With it, it does not panic.
  Yes -- I know that this is NOT the right way to fix it.  But I haven't
  been able to get it to panic yet (which confuses me).  I am going to
  be looking into the vgone() code now, as that may be a part of it.
  
  Revision  Changes    Path
  1.20      +11 -3     src/sys/miscfs/procfs/procfs_subr.c