I guess I live in a different world. I do lots of things I'm not
"supposed" to do.
Moreover, it is very sensible and usable to mprotect malloc pages. I
have implemented simple sandboxing this way. For my dissertation I
implemented a DSM by mprotect'g malloc'd memory. This system worked for
>6 on several version of Linux and SunOS. I actually have a better
track record for this technique than for some things that are within the
specifications.
Andreas Schwab wrote:
"Vincent W. Freeh" <[email protected]> writes:
The point of the code is to show that one can protect malloc code.
You "can" do many things. But that does not mean that you always get any
sensible behaviour.
Andreas.
-
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/
- References:
- Re: Understanding Linux addr space, malloc, and heap
- Re: Understanding Linux addr space, malloc, and heap
- Re: Understanding Linux addr space, malloc, and heap
- Re: Understanding Linux addr space, malloc, and heap
- Re: Understanding Linux addr space, malloc, and heap
- Re: Understanding Linux addr space, malloc, and heap
[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]