From owner-freebsd-current@FreeBSD.ORG  Wed Sep 29 08:20:07 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 140FE16A4CE; Wed, 29 Sep 2004 08:20:07 +0000 (GMT)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP
	id AE37F43D3F; Wed, 29 Sep 2004 08:20:05 +0000 (GMT)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa18521@salmon>; 29 Sep 2004 09:18:06 +0100 (BST)
To: "M. Warner Losh" <imp@bsdimp.com>
In-reply-to: Your message of "Wed, 29 Sep 2004 00:47:54 MDT."
             <20040929.004754.129577385.imp@bsdimp.com> 
X-Request-Do: 
Date: Wed, 29 Sep 2004 09:18:05 +0100
From: David Malone <dwmalone@maths.tcd.ie>
Message-ID: <200409290918.aa18521@salmon.maths.tcd.ie>
cc: ma@dt.e-technik.uni-dortmund.de
cc: matthias.andree@gmx.de
cc: re@freebsd.org
cc: current@freebsd.org
cc: developers@freebsd.org
Subject: Re: FreeBSD 5.3-BETA6 available 
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: Wed, 29 Sep 2004 08:20:07 -0000

> : Please do not close the PR yet, the bug persists in FreeBSD
> : 4.10-RELEASE-p3 (tested a few minutes ago) and probably also in 4.8.

> Does it persist in RELENG_4?

Yes - Matthias and I had a quick go at backporting Bruce's patch,
but it looks like it isn't a straight back port because some code
doesn't fill out the offset field. Triggering the bug involves root
(or someone who can write to disk devices) doing some slightly
unusual things, so it shouldn't bite people in general. If Matthias
and I get a working patch, I'll look at committing it.

	David.