From owner-freebsd-current  Wed Dec 11 19:43:48 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id TAA06499
          for current-outgoing; Wed, 11 Dec 1996 19:43:48 -0800 (PST)
Received: from pat.idt.unit.no (0@pat.idt.unit.no [129.241.103.5])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA06475;
          Wed, 11 Dec 1996 19:43:36 -0800 (PST)
Received: from idt.unit.no (tegge@ikke.idt.unit.no [129.241.111.65])
          by pat.idt.unit.no (8.8.4/8.8.4) with ESMTP
	  id EAA03905; Thu, 12 Dec 1996 04:43:26 +0100 (MET)
Message-Id: <199612120343.EAA03905@pat.idt.unit.no>
To: dyson@FreeBSD.ORG, dyson@dyson.iquest.net
Cc: jgreco@solaria.sol.net, current@FreeBSD.ORG
Subject: Re: mlocking an mmap'ped region?
In-Reply-To: Your message of "Wed, 11 Dec 1996 12:27:45 -0500 (EST)"
References: <199612111727.MAA03619@dyson.iquest.net>
X-Mailer: Mew version 1.06 on Emacs 19.33.1
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Thu, 12 Dec 1996 04:43:25 +0100
From: Tor Egge <Tor.Egge@idt.ntnu.no>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > The following does not seem to work on a 2.2-CURRENT box (built yesterday).
> > It does seem to work on SunOS.
> > 
> > Is it just too early to be doing programming or is there really something
> > preventing me from doing this?
> > 
> Yep, it is called broken code :-(.  That problem was just brought to my
> attention yesterday.  Unfortunately, someone also wants it fixed in 2.1.X :-(.
This looks similar to PR kern/1514. There is also a fix in -current
to avoid crashes after having used mlock() if the process exits without
first unlocking the memory. (added in rev 1.129 of sys/i386/i386/pmap.c,
and not present in the 2.2 branch)

- Tor Egge