From owner-freebsd-current@FreeBSD.ORG Fri Jul 16 05:22:30 2004 Return-Path: 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 EB13416A4CE for ; Fri, 16 Jul 2004 05:22:30 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDD5843D45 for ; Fri, 16 Jul 2004 05:22:30 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 7EC8614316; Fri, 16 Jul 2004 00:22:30 -0500 (CDT) Date: Fri, 16 Jul 2004 00:22:30 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: freebsd-current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Fri, 16 Jul 2004 13:26:55 +0000 Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jul 2004 05:22:31 -0000 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