From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7275 invoked by alias); 4 Dec 2013 09:56:31 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 7229 invoked by uid 48); 4 Dec 2013 09:56:28 -0000 From: "bugdal at aerifal dot cx" To: glibc-bugs@sourceware.org Subject: [Bug libc/16291] feature request: provide simpler ways to compute stack and tls boundaries Date: Wed, 04 Dec 2013 09:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bugdal at aerifal dot cx X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg00049.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=16291 --- Comment #3 from Rich Felker --- The stack is never truly unlimited. There's a finite distance in address space between the stack and the next adjacent VMA which inherently limits stack growth. And the kernel only reserved a certain virtual address range in which new mmaps won't be placed. But interpreting a stack limit of RLIM_INFINITY does require making assumptions about how the kernel treats it, which might be invalidated by changes in the kernel. So it's not easy. Can you clarify why you need to know the max size the stack might grow to, rather than the currently valid stack range? The latter would be much easier to obtain, and the former could (I think) become wrong if the application uses setrlimit between the time the stack size is obtained and the time your code needs to know it. -- You are receiving this mail because: You are on the CC list for the bug.