Date: 06 Mar 2002 23:57:24 +0000 From: Harry Newton <harry_newton@telinco.co.uk> To: freebsd-stable@FreeBSD.ORG Subject: Re: reproducable panic with python Message-ID: <86y9h55jx7.fsf@basilisk.locus> In-Reply-To: <867koq7gp7.fsf@basilisk.locus> References: <867koq7gp7.fsf@basilisk.locus>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> Harry Newton <harry_newton@telinco.co.uk> wrote:
> With this:
>
> #!/usr/local/bin/python2.2
>
> import mmap
> m = mmap.mmap(-1,256,mmap.MAP_ANON)
>
> m = 1
>
> I can panic the kernel.
Actually, all you need is:
#!/usr/local/bin/python2.2
import mmap
m = mmap.mmap(-1,256,mmap.MAP_ANON)
and if you want a version that doesn't cause a panic,
#!/usr/local/bin/python2.2
import mmap
m = mmap.mmap(-1,256,mmap.MAP_ANON)
m.close()
where the close method closes the file associated with the memory map
( which doesn't really exist with MAP_ANONYMOUS ). Looking at the
back-trace, I reckon that the mmap.close method calls msync(2), which
is where the fatal call to vm_map_clean is.
- Harry
--
Harry Newton
harry_newton at telinco.co.uk
www.gaudeamus.telinco.co.uk/html/gpg.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86y9h55jx7.fsf>