From owner-freebsd-bugs Sun Jul 22 16:30: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 83A3237B405 for ; Sun, 22 Jul 2001 16:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f6MNU4c39070; Sun, 22 Jul 2001 16:30:04 -0700 (PDT) (envelope-from gnats) Date: Sun, 22 Jul 2001 16:30:04 -0700 (PDT) Message-Id: <200107222330.f6MNU4c39070@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mike Barcroft Subject: Re: kern/8137: [patch] quotaoff followed by quotaon can crash system. Reply-To: Mike Barcroft Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/8137; it has been noted by GNATS. From: Mike Barcroft To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/8137: [patch] quotaoff followed by quotaon can crash system. Date: Sun, 22 Jul 2001 19:37:35 -0400 Adding to Audit-Trail. ----- Forwarded message from Mike Pritchard ----- Delivered-To: mike@freebsd.org Date: Sun, 22 Jul 2001 16:39:21 -0500 From: Mike Pritchard To: mike@FreeBSD.org Subject: Re: kern/8137: [patch] quotaoff followed by quotaon can crash system. User-Agent: Mutt/1.2.5i In-Reply-To: <200107192018.f6JKIRM85184@freefall.freebsd.org>; from mike@FreeBSD.org on Thu, Jul 19, 2001 at 01:18:27PM -0700 On Thu, Jul 19, 2001 at 01:18:27PM -0700, mike@FreeBSD.org wrote: > Synopsis: [patch] quotaoff followed by quotaon can crash system. > > State-Changed-From-To: open->feedback > State-Changed-By: mike > State-Changed-When: Thu Jul 19 13:17:55 PDT 2001 > State-Changed-Why: > > Does this problem still occur in newer versions of FreeBSD, > such as 4.3-RELEASE? The PR refers to problems with the way the quota hash table entries were being used. That all changed after the 4.4BSD-Lite{1,2} import. I've been unable to reproduce this problem under -current, so I'm pretty sure this has been fixed since the original PR (FreeBSD 2.2.7). If you don't hear anything back from the originator, I would just close it as "fixed in -current." -Mike -- Mike Pritchard mpp@FreeBSD.org or mpp@mppsystems.com ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message