From owner-freebsd-current@FreeBSD.ORG Mon Sep 29 20:29:29 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4010B106568A for ; Mon, 29 Sep 2008 20:29:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1BBB58FC19 for ; Mon, 29 Sep 2008 20:29:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id 5C0D046B5B for ; Mon, 29 Sep 2008 16:29:28 -0400 (EDT) Date: Mon, 29 Sep 2008 21:29:28 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Subject: Please test ipfw and pf uid/gid/jail rules X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 29 Sep 2008 20:29:29 -0000 Dear all: Although it didn't show up in 8.x testing to date, it turned out there was a serious stability regression in the ipfw uid/gid/jail rule implementation as a result of moving to rwlocks for inpcbinfo and inpcb. I think I've corrected the sources of the problem in 8.x and 7.x now, but it would be very helpful if people who use ipfw and pf could do some extra testing of these rules with invariants and witness enabled to see if we can't shake out any remaining problems. Thanks, Robert N M Watson Computer Laboratory University of Cambridge