Date: Mon, 21 Aug 2006 18:32:00 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: current@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: mount * 2 + umount + lookup = GEOM panic Message-ID: <20060821143200.GB50800@comp.chem.msu.su> In-Reply-To: <20060820102405.GC1326@garage.freebsd.pl> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060821143200.GB50800>