Kernel 2.4.6: Why doesn't mprotect () check ulimit/rlim?

[Rolf Fokkens]

While trying to restrict Oracle's memory claims I tried a strace while
making Oracle claim huge amounts of memory. It appears that Oracle claims
all it's memory by calling mprotect, which (unlike brk ()) doesn't check
rlim.
 
I don't know the details of this, but it seems a little buggy to me. If not
buggy, then what's the use of rlim?
 
Cheers,
 
Rolf