From owner-freebsd-current  Mon Apr 23 15:12:48 2001
Delivered-To: freebsd-current@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP
	id E23BA37B423; Mon, 23 Apr 2001 15:12:43 -0700 (PDT)
	(envelope-from iedowse@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa52217@salmon>; 23 Apr 2001 23:12:43 +0100 (BST)
To: Warner Losh <imp@harmony.village.org>
Cc: John Baldwin <jhb@FreeBSD.org>, freebsd-current@FreeBSD.org,
	"David W. Chapman Jr." <dwcjr@inethouston.net>, iedowse@maths.tcd.ie
Subject: Re: kernel core 
In-Reply-To: Your message of "Mon, 23 Apr 2001 16:08:39 MDT."
             <200104232208.f3NM8d876569@harmony.village.org> 
Date: Mon, 23 Apr 2001 23:12:42 +0100
From: Ian Dowse <iedowse@maths.tcd.ie>
Message-ID:  <200104232312.aa52217@salmon.maths.tcd.ie>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200104232208.f3NM8d876569@harmony.village.org>, Warner Losh writes:
>: 
>: Yes, but until such time as we do that we should warn people in UPDATING at
>: least.
>: 
>
>OK, but you won't like the UPDATING entry.

The bug actually looks fairly simple to fix. ffs_reload() isn't
checking if the new superblock fields are zero, so if an old fsck
zeros them out between a read-oly mount and a read-write remount,
then we get a division by zero or something later.

Ian

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