:Why? I can think of at least one instance where this is useful: using
:a file in the file system as a shared memory handle.
:
:Seems as if the programmer erroneously MADV_FREE's a file, well ... you
:only supplied the rope.
:
: -- Jason R. Thorpe <thor...@nas.nasa.gov>
My main worry here, putting it into words, is that malloc() uses
MADV_FREE all over the place. If a program gets corrupted due to
bugs in the program and winds up corrupting malloc, I worry that
the result could be bogus madvise() calls that destroy mmap()'d files
that the program happens to be using at the time. It may not be
a justifiable worry, but it is enough that I am not gung-ho about
implementing MADV_FREE on file mmaps.
-Matt
Matthew Dillon
<dil...@backplane.com>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
