Re: brk() system call, RLIMIT_AS, and RLIMIT_DATA in 32-bit compatibility mode

[Ramon de C Valle]

> Notice that from 0xc0000000 upwards it continues expanding the
> program break above 0xc0000000 up to 0xff000000 where it also starts
> failing and returning the current break. Is this an expected
> behaviour when running an application in 64-bit machine in 32-bit
> compatibility mode? Is RLIMIT_AS and RLIMIT_DATA being honoured?

I completely ignored the PER_LINUX32_3GB personality and thought this would be enforced by default in this case.

Thanks,

-- 
Ramon de C Valle / Red Hat Security Response Team
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/