Date: Thu, 12 Dec 1996 04:43:25 +0100 From: Tor Egge <Tor.Egge@idt.ntnu.no> To: dyson@FreeBSD.ORG, dyson@dyson.iquest.net Cc: jgreco@solaria.sol.net, current@FreeBSD.ORG Subject: Re: mlocking an mmap'ped region? Message-ID: <199612120343.EAA03905@pat.idt.unit.no> In-Reply-To: Your message of "Wed, 11 Dec 1996 12:27:45 -0500 (EST)" References: <199612111727.MAA03619@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612120343.EAA03905>