From owner-freebsd-bugs  Tue Apr 25 08:50:39 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id IAA18610
          for bugs-outgoing; Tue, 25 Apr 1995 08:50:39 -0700
Received: from cs.utah.edu (cs.utah.edu [128.110.4.21])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA18604
          for <freebsd-bugs@freebsd.org>; Tue, 25 Apr 1995 08:50:37 -0700
From: moore@ced.utah.edu
Received: from canyonlands.ced.utah.edu by cs.utah.edu (8.6.12/utah-2.21-cs)
	id JAA21131; Tue, 25 Apr 1995 09:50:35 -0600
Received: from ruin.ced.utah.edu by canyonlands.ced.utah.edu (4.1/SMI-4.1)
	id AA04707; Tue, 25 Apr 95 09:50:05 MDT
Received: by ruin.ced.utah.edu 
        (940816.SGI.8.6.9//ident-1.0) id JAA23780; Tue, 25 Apr 1995 09:50:04 -0600 
Date: Tue, 25 Apr 1995 09:50:04 -0600
Message-Id: <199504251550.JAA23780@ruin.ced.utah.edu>
To: freebsd-bugs@FreeBSD.org
Subject: bug in mmap / ftruncate in 041295-SNAP?
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

If this is a know problem, nevermind...

strip -x is broken in 041295-SNAP.  An immediate symptom is that
kernels that have been strip -x'ed won't boot.  The problems seems to
be an interaction between mmap'ed files and ftruncate.  strip chews on
a mapped file and ftruncates it.  After the ftruncate, the first page
of the file reverts to the original data that was in the file.  I
thought that it might have just been "undefined" to ftruncate a
mapped file, but moving the call to ftruncate () after the call to
munmap showed the same behavior.

Tim