From: Pete Zaitcev <zaitcev@redhat.com>
To: BOEBLINGEN LINUX390 <LINUX390@de.ibm.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: [s390x] Patch for execve with a mode switch
Date: Tue, 18 Mar 2003 09:51:08 -0500 [thread overview]
Message-ID: <20030318095108.A17230@devserv.devel.redhat.com> (raw)
In-Reply-To: <OFA75E38A6.F16CA542-ONC1256CED.00308E93@de.ibm.com>; from LINUX390@de.ibm.com on Tue, Mar 18, 2003 at 09:57:47AM +0100
> From: "BOEBLINGEN LINUX390" <LINUX390@de.ibm.com>
> Date: Tue, 18 Mar 2003 09:57:47 +0100
> I am not too happy with the arch_get_unmapped_area myself. I not
> happpy with the TIF_ABI_PENDING bit either, there has to be a
> way to do this in a simply and straighforward way.
> I'll keep thinking about it.
Actually, I agree, but the only way out that I see is to
add yet another macro, which replaces the second SET_PERSONALITY
on 2.5 and adds a hook for 2.4 in that place.
Current 2.5 code looks bizzare:
for (headers) {
if (is header) {
interpreter = x;
SET_PERSONALITY(elf_ex, ibcs2_interpreter);
break;
}
}
if (interpreter) {
} else {
SET_PERSONALITY(elf_ex, ibcs2_interpreter);
}
flush_old_exec();
some_more_core
SET_PERSONALITY(elf_ex, ibcs2_interpreter); // Cries for extermination!
current->mm->free_area_cache = TASK_UNMAPPED_BASE;
Spaghetti wihout goto's!! There's no way to get to the third
SET_PERSONALITY without being there once, so what does that mean?
-- Pete
next prev parent reply other threads:[~2003-03-18 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 8:57 [s390x] Patch for execve with a mode switch BOEBLINGEN LINUX390
2003-03-18 14:51 ` Pete Zaitcev [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 15:20 BOEBLINGEN LINUX390
2003-03-17 17:03 ` Pete Zaitcev
2003-03-16 0:25 Pete Zaitcev
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=20030318095108.A17230@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=LINUX390@de.ibm.com \
--cc=akpm@digeo.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