From: Andrew Morton <akpm@digeo.com>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: recent change to exit_mmap
Date: Sat, 18 Jan 2003 00:15:46 -0800 [thread overview]
Message-ID: <20030118001546.7df35e13.akpm@digeo.com> (raw)
In-Reply-To: <15913.2330.891678.16666@napali.hpl.hp.com>
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>
> I don't know why SET_PERSONALITY() came to be where it is now, but it
> does make some sense to me. One thing that comes to mind: on ia64, we
> normally don't map data segments with execute permission but for
> backwards-compatibility, we need to do that for x86 binaries. I think
> there might be a problem with that if SET_PERSONALITY() was done too
> late. Certainly something that could be fixed, but I suspect a
> similar ordering issue (perhaps on SPARC?) might have triggered the
> current placement of SET_PERSONALITY().
>
hmm. Seems that all the activities between the two first SET_PERSONALITY()
calls and the flush_old_exec() are pretty innocuous. And no mappings could
be set up there, because flush_old_exec() would remove them again.
I'll ask Dave about it.
next prev parent reply other threads:[~2003-01-18 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 6:05 recent change to exit_mmap Anton Blanchard
2003-01-18 6:44 ` Andrew Morton
2003-01-18 7:42 ` David Mosberger
2003-01-18 7:53 ` Andrew Morton
2003-01-18 7:58 ` David Mosberger
2003-01-18 8:15 ` Andrew Morton [this message]
2003-01-18 8:15 ` David Mosberger
2003-01-18 7:00 ` Andrew Morton
2003-01-18 7:23 ` Anton Blanchard
2003-01-18 10:44 ` Andrew Morton
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=20030118001546.7df35e13.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=anton@samba.org \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
/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