From owner-freebsd-stable@FreeBSD.ORG Tue Mar 2 16:23:36 2004 Return-Path: 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 CEEB816A4CE; Tue, 2 Mar 2004 16:23:36 -0800 (PST) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7D5243D1D; Tue, 2 Mar 2004 16:23:35 -0800 (PST) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.249.244) by smtp01.syd.iprimus.net.au (7.0.024) id 402BA927005E9AEB; Wed, 3 Mar 2004 11:23:15 +1100 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 73A484162; Wed, 3 Mar 2004 11:25:36 +1100 (EST) Date: Wed, 3 Mar 2004 11:25:36 +1100 From: Tim Robbins To: =?unknown-8bit?Q?Pawe=B3_Ma=B3achowski?= Message-ID: <20040303002536.GA59500@cat.robbins.dropbear.id.au> References: <20040302213936.216CB5F103@shellma.zin.lublin.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040302213936.216CB5F103@shellma.zin.lublin.pl> User-Agent: Mutt/1.4.1i cc: stable@freebsd.org cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: Using read-only NULLFS leads to panic. gdb output included, easy to reproduce. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 00:23:36 -0000 On Tue, Mar 02, 2004 at 10:39:36PM +0100, Pawe Maachowski wrote: > > I know NULLFS is documented as broken and incoming PRs are usually put > in suspended state, awaiting a patch. > However, there are people claiming that using NULLFS in read-only mode > is safe. It seems, they are wrong. [...] > Environmnet: > (A) FreeBSD 4.9-RELEASE, null.ko. > (B) FreeBSD 4.9-STABLE, NULLFS, almost GENERIC (+IPFIREWALL, IPFILTER...) > (C) FreeBSD 4.8-RELEASE, GENERIC, nullfs.ko (+ipfw.ko) [...] There are known bugs in nullfs in all 4.x releases to date, and in 5.0. If I have time, I may MFC the fixes some time before 4.10 is released. Can you reproduce these problems on 5.1 or 5.2? Tim