From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 11:09:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62D6616A4CE for ; Wed, 1 Dec 2004 11:09:07 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id B9A7B43D58 for ; Wed, 1 Dec 2004 11:09:06 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 45280 invoked from network); 1 Dec 2004 11:09:05 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 1 Dec 2004 11:09:05 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB1B94q3078048; Wed, 1 Dec 2004 12:09:04 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB1B94cM078047; Wed, 1 Dec 2004 12:09:04 +0100 (CET) (envelope-from pho) Date: Wed, 1 Dec 2004 12:09:04 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041201110904.GA78023@peter.osted.lan> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> <20041123013054.GA38804@peter.osted.lan> <20041130013802.J85758@mail.chesapeake.net> <20041130075602.GA72926@peter.osted.lan> <20041201054925.N18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201054925.N18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 11:09:07 -0000 On Wed, Dec 01, 2004 at 05:51:11AM -0500, Jeff Roberson wrote: > On Tue, 30 Nov 2004, Peter Holm wrote: > > > On Tue, Nov 30, 2004 at 01:39:01AM -0500, Jeff Roberson wrote: > > > > > > On Tue, 23 Nov 2004, Peter Holm wrote: > > > > > > > On Mon, Nov 22, 2004 at 06:46:50AM -0500, Jeff Roberson wrote: > > > > > On Mon, 22 Nov 2004, Ivan Voras wrote: > > > > > > > > > > > Jeff Roberson wrote: > > > > > > > > > > > > > The short description: > > > > > > > This patch removes Giant from the read(), write(), and fstat() syscalls, > > > > > > > as well as page faults, and bufdone (io interrupts) when using FFS. It > > > > > > > > > > > > What is the plan re: RELENG_5? Will things like this (giantless vm, fs) > > > > > > be merged into it? > > > > > > > > > > The giantless vm was already merged back to RELENG_5 and enabled on amd64, > > > > > and i386. I hope to merge the giantless vfs back after a month or so of > > > > > no problems on -current. I hope to commit it to -current this week. > > > > > > > > > > I haven't received any feedback from the list though. I hope people are > > > > > testing it. Perhaps the silence indicates universal success? :-) > > > > > > > > > > > > > Here's a problem I ran into during stress test: > > > > > > > > http://www.holm.cc/stress/log/jeff01.html > > > > > > > > Let me know if you need more gdb output. > > > > > > Thanks, this is the most serious bug of the couple that were reported. It > > > indicates a possible race to flush a buffer. I'm still looking for this. > > > What steps did you take to produce this panic? > > > > > > > I ran my kernel stress test: http://www.holm.cc/stress/src/stress.tgz > > I stopped using your patch after the two reported problems. > > Let me know if you would like me to perform more testing with your patch. > > Thanks, I think I may have fixed the problems that were exposed via your > stress tool. I'll post an updated patch to the list in a moment. I'll test it ASAP. > I was > wondering if you have seen a panic in pmap_invalidate_range via sigexit()? > It seems to have been caused by illegal calls to sigexit() from > trapsignal(). If you have not reported it yet, I have a copy of a stack > here and I can let the responsible people know. > This is a problem I have not encountered, so please do. Regards, - Peter