From tim@robbins.dropbear.id.au  Tue Mar  2 16:23:36 2004
Return-Path: <tim@robbins.dropbear.id.au>
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)
Message-Id: <20040303002536.GA59500@cat.robbins.dropbear.id.au>
Date: Wed, 3 Mar 2004 11:25:36 +1100
From: Tim Robbins <tjr@freebsd.org>
To: =?unknown-8bit?Q?Pawe=B3_Ma=B3achowski?= <pawmal-posting@freebsd.lublin.pl>
Cc: FreeBSD-gnats-submit@freebsd.org, stable@freebsd.org
In-Reply-To: <20040302213936.216CB5F103@shellma.zin.lublin.pl>
Subject: Re: Using read-only NULLFS leads to panic. gdb output included, easy to reproduce.
References: <20040302213936.216CB5F103@shellma.zin.lublin.pl>

>Number:         63669
>Category:       kern
>Synopsis:       Re: Using read-only NULLFS leads to panic. gdb output included, easy to reproduce.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 02 16:30:18 PST 2004
>Closed-Date:    Thu Apr 01 10:48:12 PST 2004
>Last-Modified:  Thu Apr 01 10:48:12 PST 2004
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 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
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Thu Apr 1 10:47:44 PST 2004 
State-Changed-Why:  
Misfiled followup to kern/63662; text has been copied over. 


Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Apr 1 10:47:44 PST 2004 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=63669 
>Unformatted:
