From owner-freebsd-current@FreeBSD.ORG  Fri Jul 16 20:08:52 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 83D4F16A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 16 Jul 2004 20:08:52 +0000 (GMT)
Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net
	[207.115.63.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2E61643D39
	for <freebsd-current@freebsd.org>;
	Fri, 16 Jul 2004 20:08:52 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from elischer.org (adsl-68-121-219-69.dsl.snfc21.pacbell.net
	[68.121.219.69])i6GK8nUK189578;	Fri, 16 Jul 2004 16:08:50 -0400
Message-ID: <40F835D0.8070609@elischer.org>
Date: Fri, 16 Jul 2004 13:08:48 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Mark Linimon <linimon@lonesome.com>
References: <Pine.LNX.4.44.0407160008280.20163-100000@pancho>
In-Reply-To: <Pine.LNX.4.44.0407160008280.20163-100000@pancho>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: Call for PRs: nullfs
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2004 20:08:52 -0000

Mark Linimon wrote:

>Although there has been much discussion of the bugginess of nullfs
>on the mailing lists in the past, there are actually only a few PRs
>about it.  Perhaps it's time to figure out what errors still exist
>as we contemplate 5-STABLE.
>
>I have taken the liberty of going through the PR database to ensure
>that any PR involving the operation of nullfs or mount_null (other
>than simply referring to them in documentation, etc.) have the 'nullfs'
>string in the Synopsis.  From my count, these are the following:
>
>  kern/28206 (5.0-CURRENT)
>  kern/28566 (4.3)
>  kern/51583 (confirmed still a problem in -STABLE, -CURRENT)
>  kern/59945 (4.9)
>  bin/59569  (5.1)
>  kern/63662 (fixed in -CURRENT, not yet backported)
>
>If anyone has others with either 4.10, -STABLE, or -CURRENT, I would
>like to ask that they submit them (with the 'nullfs' keyword in the
>Synopsis) so that we can figure out where we are.
>
>Thanks.
>
>mcl
>
>_______________________________________________
>freebsd-current@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>  
>
I'm using nullfs for jails on -4.8(ish) without problems so far..

I'm only using a subset of functionality..
e.g.. files looked at in the jail are never looked at by
another jail or by the base system.