linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sposelenov@emcraft.com (Sergei Poselenov)
To: linux-arm-kernel@lists.infradead.org
Subject: clone() for 2.6.33 Cortex-M3 kernel?
Date: Sat, 28 May 2011 14:59:25 +0400	[thread overview]
Message-ID: <1306580365.749.1.camel@mehome> (raw)

Hello all,

I'm trying to implement the pthread support for a Cortex-M3
Thumb target using the CodeSourcery uclibc toolchain.

I faced the following problem: a simple clone() test program
crashes the system. As I found, the problem is that the 
stack for the new clone process, which is passed to the clone()
syscall, returns incorrectly for the new process (32 bytes higher)
and the pointer to the clone function and argument, which are saved
in the new clone stack, clobbered.

Is it a known issue?

In the kernel configuration, the CONFIG_CPU_V7M and CONFIG_ARM_THUMB
are enabled.



Thanks for any help.

Regards,
Sergei

                 reply	other threads:[~2011-05-28 10:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1306580365.749.1.camel@mehome \
    --to=sposelenov@emcraft.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).