Yes, this has been fixed. Python was using MAP_ANON|MAP_NOSYNC
mmap()'s and this resulted in the possibility of msync() encountering
an optimized vm_map_entry that did not yet have a VM object associated
with it, causing a panic.
Both -stable and -current have been fixed to handle the case.
-current was fixed on March 7th, and -stable on March 8th.
-Matt
:On Wed, 6 Mar 2002, David Malone wrote:
:
:> On Tue, Mar 05, 2002 at 11:11:48PM +0000, Harry Newton wrote:
:> > #!/usr/local/bin/python2.2
:> >
:> > import mmap
:> > m = mmap.mmap(-1,256,mmap.MAP_ANON)
:> > m = 1
:>
:> I've made a little progress on this. It doesn't work with python2.0.
:> It does work on both -stable and -current. The trace back on -current
:> looks is included below. It's doing a msync when it doesdies.
:
:{...}
:
:I've not seen any followup concerning resolution of this - have any
:conclusions been reached?
:
:--
:Andrew I MacIntyre "These thoughts are mine alone..."
:E-mail: [EMAIL PROTECTED] | Snail: PO Box 370
: [EMAIL PROTECTED] | Belconnen ACT 2616
:Web: http://www.andymac.org/ | Australia
:
:
:To Unsubscribe: send mail to [EMAIL PROTECTED]
:with "unsubscribe freebsd-stable" in the body of the message
:
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
