From owner-freebsd-stable@FreeBSD.ORG  Mon Mar  8 00:59:10 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 B64C616A4CE; Mon,  8 Mar 2004 00:59:10 -0800 (PST)
Received: from mizar.origin-it.net (mizar.origin-it.net [194.8.96.234])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 240F443D1D; Mon,  8 Mar 2004 00:59:10 -0800 (PST)
	(envelope-from helge.oldach@atosorigin.com)
Received: from matar.hbg.de.int.atosorigin.com (dehsfw3e.origin-it.net
	[194.8.96.68])i288wnq5039474
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 8 Mar 2004 09:58:49 +0100 (CET)
	(envelope-from helge.oldach@atosorigin.com)
Received: from galaxy.hbg.de.ao-srv.com (galaxy.hbg.de.ao-srv.com
	[161.89.20.4])ESMTP id i288wnRF068553;
	Mon, 8 Mar 2004 09:58:49 +0100 (CET)
	(envelope-from helge.oldach@atosorigin.com)
Received: (from hmo@localhost)
	by galaxy.hbg.de.ao-srv.com (8.9.3p2/8.9.3/hmo30mar03) id JAA18049;
	Mon, 8 Mar 2004 09:58:48 +0100 (MET)
Message-Id: <200403080858.JAA18049@galaxy.hbg.de.ao-srv.com>
In-Reply-To: <20040303134001.GA63144@cat.robbins.dropbear.id.au> from Tim
	Robbins at "Mar 3, 2004  2:40: 1 pm"
To: tjr@freebsd.org (Tim Robbins)
Date: Mon, 8 Mar 2004 09:58:47 +0100 (MET)
From: Helge Oldach <helge.oldach@atosorigin.com>
X-Address: Atos Origin GmbH, Friesenstraße 13, D-20097 Hamburg, Germany
X-Phone: +49 40 7886 7464, Fax: +49 40 7886 9464, Mobile: +49 160 4782517
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
cc: pawmal-posting@freebsd.lublin.pl
cc: stable@freebsd.org
cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: Using read-only NULLFS leads to panic. gdb output included, e
	asy to reproduce.
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2004 08:59:10 -0000

Hi,

Tim Robbins:
>On Wed, Mar 03, 2004 at 12:09:30PM +0100, Pawel Malachowski wrote:
>
>> On Wed, Mar 03, 2004 at 11:25:36AM +1100, Tim Robbins wrote:
>> 
>> > 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.
>> 
>> Sounds interesting.
>> 
>> > Can you reproduce these problems on 5.1 or 5.2?
>> 
>> Procedure:
>> mount_null -o ro /usr/ports /mnt/1
>> find /usr/ports -type f -perm -u+s &
>> find /mnt/1 -type f -perm -u+s &
>> ...
>> <about 30-40 processess of find(1) was enough>
>> 
>> 
>> I was not able to reproduce panic on 5.1-RELEASE system.
>> 
>> However, I've reproduced second problem described in this PR,
>> which happened to me on 4.9-STABLE once.
>[...]
>
>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.

Did I miss this MFC, or haven't you back-ported it yet?

Thanks!

Helge