Date: Wed, 11 Dec 1996 20:40:08 -0800 From: David Greenman <dg@root.com> 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? Message-ID: <199612120440.UAA13311@root.com> In-Reply-To: Your message of "Thu, 12 Dec 1996 04:43:25 %2B0100." <199612120343.EAA03905@pat.idt.unit.no>
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) 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612120440.UAA13311>