From: Andreas Schwab <schwab@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix has_holes mprotect in dl-load.c
Date: Tue, 06 Jul 2004 22:42:00 -0000 [thread overview]
Message-ID: <jeoems3gi2.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040706182508.GF5191@sunsite.ms.mff.cuni.cz> (Jakub Jelinek's message of "Tue, 6 Jul 2004 20:25:08 +0200")
Jakub Jelinek <jakub@redhat.com> writes:
> Hi!
>
> l_text_end is not set at this point yet and even if it would,
> if first PT_LOAD segment is not executable, it would still be 0.
> Doing mprotect (0, up to few MB, PROT_NONE) is bad and
> mprotecting l->l_laddr + c->mapend is really what is needed.
See <http://sources.redhat.com/ml/libc-hacker/2004-05/msg00033.html>.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-07-06 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 20:40 Jakub Jelinek
2004-07-06 22:42 ` Andreas Schwab [this message]
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=jeoems3gi2.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@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).