linux-origin
[Top] [All Lists]

Re: My sys32_execve().

To: ralf@xxxxxxxxxxx (Ralf Baechle)
Subject: Re: My sys32_execve().
From: kanoj@xxxxxxxxxxxxxxxxxxx (Kanoj Sarcar)
Date: Wed, 1 Mar 2000 15:34:15 -0800 (PST)
Cc: ralf@xxxxxxxxxxx (Ralf Baechle), ulfc@xxxxxxxxxxxxxxxxxxxx (Ulf Carlsson), kanoj@xxxxxxxxxxxxxxxxxxxx (Kanoj Sarcar), linux-origin@xxxxxxxxxxx
In-reply-to: <20000302001922.A4992@xxxxxxxxxxxxxx> from "Ralf Baechle" at Mar 02, 2000 12:19:22 AM
Sender: owner-linux-origin@xxxxxxxxxxx
> 
> On Wed, Mar 01, 2000 at 03:06:37PM -0800, Kanoj Sarcar wrote:
> 
> > Umm, didn't I just check this in a couple of days back?
> 
> Not unless you are better at hacking than the NSA because this code has
> never reached a machine connected to the net :-)

No no, I meant a version of sys32_execve, not the exact code that
you sent.

Actually, if you look at the checked in version of sys32_execve, it is
quite different from the sparc version (_much_ less code).

Seeing that there are probably more people working on the ia32
compatibility issues for ia64, I have decided I am going to look 
at how they have converted a system call first, then look at the
sparc implementation, and decide which one I want to pick.

While we are at it, maybe its time we came up with rules for
determining which system calls need to be 32bitized. Other things
like TASK_SIZE also probably need to be 32bitized (similar to 
TASK_UNMAPPED_BASE).

Kanoj

> 
> The similarity is natural, I just sent this for your interest because of
> yesterday's phone discussion about the egcs bug and workaround.
> 
>   Ralf
> 


<Prev in Thread] Current Thread [Next in Thread>