From: Erik de Castro Lopo <erikd@mega-nerd.com>
To: ultralinux@vger.kernel.org
Subject: Re: SMP Sparc64 : bug in clone?
Date: Mon, 25 Mar 2002 07:53:55 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-101704299721261@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-101684978515837@msgid-missing>
On Sat, 23 Mar 2002 13:15:45 +1100
Erik de Castro Lopo <nospam@mega-nerd.com> wrote:
> Hi all,
>
> The clone system call on Sparc64 Linux seems to be producing drastically
> different results to those obtain in x86 linux. On Sparc64 it seems as if
> the child process never runs (tried on uni-processor 2.4.18 and SMP
> 2.4.19-pre4 with the same results).
A collegue of mine suggested that it may be failing because the stack was
not executable. I therefore wrote a new test where memory for the stack
was allocated using an anonymous mmap().
Like the others, this program runs on x86 but does not on Sparc64.
New test program here:
https://mega-nerd.net/clone_mmap_test.c
A similar program using fork() works as expected.
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam@mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
"The reasonable man adapts himself to the world; the unreasonable one
persists to adapt the world to himself. Therefore all progress depends
on the unreasonable man." -- George Bernard Shaw (1856-1950)
next prev parent reply other threads:[~2002-03-25 7:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-23 2:15 SMP Sparc64 : bug in clone? Erik de Castro Lopo
2002-03-23 3:33 ` Erik de Castro Lopo
2002-03-25 7:53 ` Erik de Castro Lopo [this message]
2002-03-25 8:12 ` David S. Miller
2002-03-25 8:35 ` Erik de Castro Lopo
2002-03-25 8:36 ` David S. Miller
2002-04-29 20:14 ` David S. Miller
2002-04-29 20:17 ` Erik de Castro Lopo
2002-05-04 23:08 ` Erik de Castro Lopo
2002-05-06 14:25 ` Noah Beck
2002-05-06 21:36 ` Erik de Castro Lopo
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=marc-linux-ultrasparc-101704299721261@msgid-missing \
--to=erikd@mega-nerd.com \
--cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.