From owner-freebsd-current  Wed Dec 11 20:40:56 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id UAA12939
          for current-outgoing; Wed, 11 Dec 1996 20:40:56 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA12911;
          Wed, 11 Dec 1996 20:40:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id UAA13311; Wed, 11 Dec 1996 20:40:08 -0800 (PST)
Message-Id: <199612120440.UAA13311@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Tor Egge <Tor.Egge@idt.ntnu.no>
cc: dyson@freebsd.org, jgreco@solaria.sol.net, current@freebsd.org
Subject: Re: mlocking an mmap'ped region? 
In-reply-to: Your message of "Thu, 12 Dec 1996 04:43:25 +0100."
             <199612120343.EAA03905@pat.idt.unit.no> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 11 Dec 1996 20:40:08 -0800
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)

   Uh, actually, it is in the 2.2 branch. See rev 1.128.2.1 of pmap.c

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project