public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/12416] Dynamic linker incorrectly reduces the stack size when making it executable
Date: Wed, 19 Jan 2011 19:25:00 -0000	[thread overview]
Message-ID: <bug-12416-131-lOZx3CFdmk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12416-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12416

Roland McGrath <roland at gnu dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |roland at gnu dot org

--- Comment #2 from Roland McGrath <roland at gnu dot org> 2011-01-19 18:53:23 UTC ---
Changing the page protections splits the mapping into two mappings.  There is
no other way it could be in the kernel.  The mapping is the granularity at
which page protections are managed.  The /proc/pid/maps output is arguably
wrong because after the split, only the lower mapping displays as [stack].  

But pthread_getattr_np doesn't pay attention to the [stack] magic name anyway,
it just looks at addresses.  So pthread_getattr_np needs to look at multiple
contiguous mappings after the one containing __libc_stack_end if the intent is
that its results are consistent after a protection change.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-01-19 18:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 18:29 [Bug nptl/12416] New: " kumpera at gmail dot com
2011-01-19 18:53 ` [Bug nptl/12416] " drepper.fsp at gmail dot com
2011-01-19 19:25 ` roland at gnu dot org [this message]
2011-01-19 20:35 ` kumpera at gmail dot com
2012-05-26  4:32 ` siddhesh at redhat dot com
2012-05-26 15:31 ` kumpera at gmail dot com
2012-05-28  5:27 ` siddhesh at redhat dot com
2012-10-03 18:18 ` siddhesh at redhat dot com
2014-06-27 14:03 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-12416-131-lOZx3CFdmk@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).