From owner-freebsd-bugs@FreeBSD.ORG Wed Oct 13 23:32:36 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7269916A4CE; Wed, 13 Oct 2004 23:32:36 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43A4443D45; Wed, 13 Oct 2004 23:32:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 287CA5150F; Wed, 13 Oct 2004 16:32:35 -0700 (PDT) Date: Wed, 13 Oct 2004 16:32:35 -0700 From: Kris Kennaway To: Ceri Davies , "Simon L. Nielsen" , tutoren@physik.TU-Berlin.DE, freebsd-bugs@FreeBSD.org Message-ID: <20041013233234.GA29910@xor.obsecurity.org> References: <200410131248.i9DCmdQq001303@freefall.freebsd.org> <20041013130113.GO57641@submonkey.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: <20041013130113.GO57641@submonkey.net> User-Agent: Mutt/1.4.2.1i Subject: Re: kern/72636: Detaching USB-Memorystick without prior umount can cause System panic X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2004 23:32:36 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 13, 2004 at 02:01:13PM +0100, Ceri Davies wrote: > On Wed, Oct 13, 2004 at 12:48:39PM +0000, Simon L. Nielsen wrote: > > Synopsis: Detaching USB-Memorystick without prior umount can cause Syst= em panic > >=20 > > State-Changed-From-To: open->closed > > State-Changed-By: simon > > State-Changed-When: Wed Oct 13 12:45:41 GMT 2004 > > State-Changed-Why:=20 > > This is a known problem which is mentioned many times in the mail > > archives, and probably also in few PR's. People are working towards > > fixing this problem, but it's far from trivial. > > Close the PR since this is a well known long term TODO/TOFIX item. >=20 > It should be either left open, or suspended at worst, until this is > corrected. If someone is working on it, assign the PR to them, but do > not close problem reports for problems that are still ongoing please. That encourages duplicate PRs :) Shouldn't you leave the earliest PR describing the problem open, and close the rest with pointers to it? Kris --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBbbsSWry0BWjoQKURAm/IAKDOSSMIvbEaaJz2JGOIdr7w0TQfKgCg1dm/ vQQD7Z5Dx4Cjauqp+qvpzBk= =BumT -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3--