From owner-freebsd-bugs  Mon Jun  4 14:40:15 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 6712837B405
	for <freebsd-bugs@hub.freebsd.org>; Mon,  4 Jun 2001 14:40:07 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.3/8.11.3) id f54Le7b15492;
	Mon, 4 Jun 2001 14:40:07 -0700 (PDT)
	(envelope-from gnats)
Date: Mon, 4 Jun 2001 14:40:07 -0700 (PDT)
Message-Id: <200106042140.f54Le7b15492@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Kris Kennaway <kris@obsecurity.org>
Subject: Re: kern/25974: Holes in files do not zero-fill
Reply-To: Kris Kennaway <kris@obsecurity.org>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR kern/25974; it has been noted by GNATS.

From: Kris Kennaway <kris@obsecurity.org>
To: Jim Zelenka <jimz@panasas.com>
Cc: Kris Kennaway <kris@obsecurity.org>,
	freebsd-gnats-submit@freebsd.org
Subject: Re: kern/25974: Holes in files do not zero-fill
Date: Mon, 4 Jun 2001 14:36:27 -0700

 On Sat, Jun 02, 2001 at 04:45:08PM -0400, Jim Zelenka wrote:
 > >For some reason this response did not appear in GNATS.  I asked Dima
 > >to re-forward it.
 > 
 > That's probably my fault; I sent two responses. In the first, I said
 > that I'd checked briefly, and I didn't see the problem. In the
 > second one, I said that more extensive testing made the problem
 > appear. The problem is particularly likely to occur on busy systems
 > or systems where lots of files were created and deleted between
 > runs of the test program. I suspect that the problem is that something
 > is not zeroing out a block that is getting reallocated, and so
 > old bits are coming back, but that's only based on empirical observation,
 > and not a reading of the code.
 
 We did fix a bug with this kind of symptoms a while back (and released
 an advisory; perhaps that is related?)
 
 Kris

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message