From owner-cvs-sys  Tue May 12 10:37:47 1998
Return-Path: <owner-cvs-sys>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA12355
          for cvs-sys-outgoing; Tue, 12 May 1998 10:37:47 -0700 (PDT)
          (envelope-from owner-cvs-sys)
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 KAA12298;
          Tue, 12 May 1998 10:37:35 -0700 (PDT)
          (envelope-from bde@FreeBSD.org)
From: Bruce Evans <bde@FreeBSD.ORG>
Received: (from bde@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA25939;
	Tue, 12 May 1998 10:34:05 -0700 (PDT)
Date: Tue, 12 May 1998 10:34:05 -0700 (PDT)
Message-Id: <199805121734.KAA25939@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG
Subject: cvs commit: src/sys/i386/i386 autoconf.c src/sys/kern
         kern_shutdown.c
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

bde         1998/05/12 10:34:04 PDT

  Modified files:
    sys/i386/i386        autoconf.c 
    sys/kern             kern_shutdown.c 
  Log:
  Backed out previous commit.  It is invalid to call d_ioctl() on
  possibly non-open devices, and we don't want to restrict dumping
  to swap devices anwyay.  It is especially invalid to call d_ioctl()
  in non-process context for panics.  d_psize() can be called on
  non-open devices, at least on non-SLICED ones that support d_dump(),
  and setdumpdev() has depended on this for a long time although it
  is probably wrong, but even d_psize() can't be called in non-process
  context - that's why dumpsys() depends on previously computed values
  although these values may be stale.  The historical restriction to
  devices with dkpart(dev) == SWAP_PART should go away.
  
  Revision  Changes    Path
  1.97      +2 -5      src/sys/i386/i386/autoconf.c
  1.31      +3 -8      src/sys/kern/kern_shutdown.c