> Do you count applications which selectively mprotect()'s memory (to
> trap SIGSEGV and maintain coherency with on-disk data structures) as
> "broken applications"?
>
> Such applications *can* use large amounts of mprotect()'s.
That would explain a lot since mprotect currently doesn't seem to do
merging, and worse it also seems to not be doing rlimit checking right
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Aug 07 2001 - 21:00:38 EST