From owner-freebsd-current  Wed Dec 11 09:29:19 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id JAA23513
          for current-outgoing; Wed, 11 Dec 1996 09:29:19 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA23504;
          Wed, 11 Dec 1996 09:29:08 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id MAA03619; Wed, 11 Dec 1996 12:27:45 -0500 (EST)
From: John Dyson <dyson@dyson.iquest.net>
Message-Id: <199612111727.MAA03619@dyson.iquest.net>
Subject: Re: mlocking an mmap'ped region?
To: jgreco@solaria.sol.net (Joe Greco)
Date: Wed, 11 Dec 1996 12:27:45 -0500 (EST)
Cc: current@freebsd.org, dyson@freebsd.org
In-Reply-To: <199612111636.KAA03706@solaria.sol.net> from "Joe Greco" at Dec 11, 96 10:35:59 am
Reply-To: dyson@freebsd.org
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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 :-(.

I'll probably get it fixed in -current in the next day or so.  Doing mlock
the way that it is currently done is problematical from a couple of viewpoints,
so I think it is going to need to be reworked.  Basically, the original
way of doing vm_map_pageable is wrong for userland pages.

(BTW, I seem to remember that someone had found this problem a year or
so ago, and it fell through the cracks.)

John