From: willy@thepuffingroup.com
To: John Marvin <jsm@udlkern.fc.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Linux syscall ABI
Date: Tue, 15 Feb 2000 01:15:11 -0500 [thread overview]
Message-ID: <20000215011511.U9944@thepuffingroup.com> (raw)
In-Reply-To: <200002150536.WAA04580@udlkern.fc.hp.com>; from John Marvin on Mon, Feb 14, 2000 at 10:36:39PM -0700
On Mon, Feb 14, 2000 at 10:36:39PM -0700, John Marvin wrote:
> > No, we don't. We're talking about PER_LINUX binaries here, and those
> > never expected to be able to dereference NULL pointers.
>
> I don't know much about PER_SVR4, and why it exists. Willy pointed it
> out to me. I can see from the kernel source that perhaps it is only there
> for sparc. If it is not necessary for parisc-linux to support then
> there is no issue. If it is necessary then I guess I assumed that PER_SVR4
> binaries would use the same gateway page as PER_LINUX binaries.
Linux has a personality() syscall which tells the kernel what operating
system this binary was compiled for. PER_SVR4 means that this binary
was compiled for SVR4. We _may_ want to include a PER_HPUX at some
point, but i'm not convinced we need it yet. I pointed you at that bit
of code to show you that for some binaries Linux did that nasty hack,
rather than to advocate we do it too.
next prev parent reply other threads:[~2000-02-15 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-15 5:36 [parisc-linux] Linux syscall ABI John Marvin
2000-02-15 6:15 ` willy [this message]
2000-02-15 12:50 ` Philipp Rumpf
2000-02-16 14:04 ` [parisc-linux] Location of HIL protocol docs? Brian S. Julin
2000-02-16 18:42 ` Grant Grundler
2000-02-15 17:25 ` [parisc-linux] Linux syscall ABI Grant Grundler
2000-02-15 18:18 ` Philipp Rumpf
2000-02-15 19:15 ` Frank Rowand
2000-02-16 2:34 ` Grant Grundler
2000-02-16 9:33 ` Kirk Bresniker
-- strict thread matches above, loose matches on Subject: below --
2000-02-17 14:17 John Marvin
2000-02-16 13:57 John Marvin
2000-02-16 17:41 ` Philipp Rumpf
2000-02-14 9:30 John Marvin
2000-02-14 13:34 ` Philipp Rumpf
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=20000215011511.U9944@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=jsm@udlkern.fc.hp.com \
--cc=parisc-linux@thepuffingroup.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