linux-kernel - Re: brk() system call, RLIMIT_AS, and RLIMIT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <83712412-35d8-473b-a27d-cf5886be71fd@zmail15.collab.prod.int.phx2.redhat.com>
Date:	Thu, 22 Dec 2011 04:46:52 -0500 (EST)
From:	Ramon de C Valle <rcvalle@...hat.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: brk() system call, RLIMIT_AS, and RLIMIT_DATA in 32-bit compatibility mode



> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/