Date: Wed, 3 Mar 2004 18:56:58 +0100 From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl> To: Tim Robbins <tjr@freebsd.org> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: Using read-only NULLFS leads to panic. gdb output included, easy to reproduce. Message-ID: <20040303175658.GA43503@shellma.zin.lublin.pl> In-Reply-To: <20040303134001.GA63144@cat.robbins.dropbear.id.au> References: <20040302213936.216CB5F103@shellma.zin.lublin.pl> <20040303002536.GA59500@cat.robbins.dropbear.id.au> <20040303110930.GA35449@shellma.zin.lublin.pl> <20040303134001.GA63144@cat.robbins.dropbear.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 04, 2004 at 12:40:01AM +1100, Tim Robbins wrote: > I'm sorry - the commit that fixed the deadlock issue you're describing > here ocurred between 5.1 and 5.2, not between 5.0 and 5.1 like I > had previously thought. Try 5.2, or try this patch on 5.1. If it solves > your problem, I'll backport it to 4.x for you later this week. I've installed 5.2.1-RC2 in place of 5.1-RELEASE on my test box. I was not able to reproduce this problem anymore. TIA, -- Paweł Małachowski
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040303175658.GA43503>