From owner-freebsd-stable@FreeBSD.ORG Sat Mar 4 09:30:12 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D14FB16A420 for ; Sat, 4 Mar 2006 09:30:12 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3314A43D49 for ; Sat, 4 Mar 2006 09:30:12 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.123.190] (ti211110a080-8691.bb.online.no [85.165.97.243]) by smtp1.powertech.no (Postfix) with ESMTP id 01F857E5A; Sat, 4 Mar 2006 10:30:11 +0100 (CET) In-Reply-To: <20060228052328.GA29811@xor.obsecurity.org> References: <20060221195601.GA63134@xor.obsecurity.org> <20060228052328.GA29811@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Frode Nordahl Date: Sat, 4 Mar 2006 10:30:08 +0100 To: Kris Kennaway X-Mailer: Apple Mail (2.746.2) Cc: stable@freebsd.org Subject: Re: Patch for quota deadlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2006 09:30:12 -0000 On 28. feb. 2006, at 06.23, Kris Kennaway wrote: > On Tue, Feb 21, 2006 at 02:56:01PM -0500, Kris Kennaway wrote: >> Jeff has been too busy to send this patch himself, but it fixed the >> quota deadlock that I was able to provoke on my machine. Does it >> also >> solve the issue for others? > > I've seen 0 feedback about this so far. Since a number of people have > reported that the quota deadlock is the only thing keeping them from > upgrading from 5.x to 6.x, I expected a more enthusiastic testing > response than this :-) > > Please, those of you who have reported this problem, test the patch > and see if it works for you. If there are further problems, we can't > fix them in time for 6.1 unless we hear about it in the next week or > so. I have not been tough enough to even try 6.x on our busy NFS servers yet, so I did not know this problem existed. This is what you get for not taking the time to test future releases I guess :-/ I will put RELENG_6 with this patch on one of them next week and report back ASAP! Does anyone have a test-case that will provoke the problem at will, so I can make some tests in a controlled environment before I put it out in the wild? Frode Nordahl frode@nordahl.net