From owner-freebsd-current@FreeBSD.ORG Mon Aug 21 14:32:36 2006 Return-Path: X-Original-To: current@FreeBSD.org 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 6965916A4E0; Mon, 21 Aug 2006 14:32:36 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6596943D4C; Mon, 21 Aug 2006 14:32:13 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id k7LEW1Gp051088; Mon, 21 Aug 2006 18:32:01 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id k7LEW0Tk051087; Mon, 21 Aug 2006 18:32:00 +0400 (MSD) (envelope-from yar) Date: Mon, 21 Aug 2006 18:32:00 +0400 From: Yar Tikhiy To: Pawel Jakub Dawidek Message-ID: <20060821143200.GB50800@comp.chem.msu.su> References: <20060818184656.GB16008@comp.chem.msu.su> <20060818191457.GA78998@xor.obsecurity.org> <20060818202508.GA88159@garage.freebsd.pl> <20060819070804.GA23066@comp.chem.msu.su> <20060820102405.GC1326@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060820102405.GC1326@garage.freebsd.pl> User-Agent: Mutt/1.5.9i Cc: current@FreeBSD.org, Kris Kennaway Subject: Re: mount * 2 + umount + lookup = GEOM panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 21 Aug 2006 14:32:36 -0000 On Sun, Aug 20, 2006 at 12:24:05PM +0200, Pawel Jakub Dawidek wrote: > On Sat, Aug 19, 2006 at 11:08:05AM +0400, Yar Tikhiy wrote: > > On Fri, Aug 18, 2006 at 10:25:08PM +0200, Pawel Jakub Dawidek wrote: > > > No, it's difficult to solve in a architectural clean way, but IMHO this > > > bug should be fixed. I've a fix for this (which allows for multiple > > > read-only mounts). It's hackish, but works. > > > > > > Unfortunately phk@ didn't agree on committing it, so next time, please > > > CC him:) > > > > Just to satisfy my curiosity: Do you have references to a discussion > > of the problem? When such a simple script triggers an architectural > > issue, the latter is definitely worth taking a glance at. :-) > > I'm not sure if this was discussed in public. Anyway, the patch is here: > > http://people.freebsd.org/~pjd/patches/mro_mount.patch > > (I hope it is up-to-date). Works for me! That is, I can no longer reproduce the panic with it applied. I'm afraid I'm too ignorant to dig the patch though. -- Yar