Linus Torvalds <[email protected]> wrote:
> > (3) Not permitting a file to be shrunk if it would truncate any shared
> > mappings (private mappings are copied).
>
> Why?
>
> Truncate is _supposed_ to get rid of any shared mmap stuff.
Yeah... but under _NOMMU_ conditions, it can't. There's no MMU around to
enforce the fact that the mapping has been shrunk.
Imagine two processes: one creates a shmem file and makes it a certain size;
both processes mmap it; then one of the processes attempts to shrink it. The
process that shrank it knows it has been shortened and that the memory has
been release, but the second process may not. Splat.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
