On Sun, Apr 24, 2016 at 1:29 PM, Konstantin Khlebnikov <koct9i@xxxxxxxxx> wrote:
>
> This patch checks current usage also against rlim_max if rlim_cur is zero.
> This is safe because task anyway can increase rlim_cur up to rlim_max.
> Size of brk is still checked against rlim_cur, so this part is completely
> compatible - zero rlim_cur forbids brk() but allows private mmap().
Ack. And I'll assume this comes through -mm like the original patches did.
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>