public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: what's parisc execve_wrapper doing in the end?
Date: Tue, 09 Oct 2012 10:55:21 +0100	[thread overview]
Message-ID: <1349776521.2615.54.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <1349695707.2615.38.camel@dabdike.int.hansenpartnership.com>

On Mon, 2012-10-08 at 12:28 +0100, James Bottomley wrote:
> Even with the patch applied, it's hanging on boot around the first
> kthread spawns.  I'm investigating.

Actually an obvious fix: you can't set up ksp and then zero the
registers.

I note that the stack frame you're creating is too big since
THREAD_SZ_ALGN includes space for a stack frame by design so adding
another one is redundant.  However, this confusion seems to permeate the
syscall code as well, so perhaps fixing it up later is better.

With this patch applied, I can now boot up successfully to a login
prompt.

James

---

diff --git a/arch/parisc/kernel/process.c b/arch/parisc/kernel/process.c
index 61113c3..38db36f 100644
--- a/arch/parisc/kernel/process.c
+++ b/arch/parisc/kernel/process.c
@@ -254,8 +254,6 @@ copy_thread(unsigned long clone_flags, unsigned long usp,
 #ifdef CONFIG_HPUX
 	extern void * const hpux_child_return;
 #endif
-	cregs->ksp = (unsigned long)stack + THREAD_SZ_ALGN + FRAME_SIZE;

  reply	other threads:[~2012-10-09  9:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121004045150.GH23473@ZenIV.linux.org.uk>
2012-10-04  9:30 ` what's parisc execve_wrapper doing in the end? James Bottomley
2012-10-05 11:07   ` James Bottomley
2012-10-05 13:44     ` James Bottomley
2012-10-05 14:47       ` James Bottomley
2012-10-05 14:48       ` Al Viro
2012-10-05 14:55         ` James Bottomley
2012-10-05 19:21           ` Al Viro
2012-10-05 23:04           ` Al Viro
2012-10-08 11:28             ` James Bottomley
2012-10-09  9:55               ` James Bottomley [this message]
2012-10-10  4:26                 ` Al Viro
2012-10-05 22:54         ` John David Anglin
2012-10-05 23:32           ` Al Viro
2012-10-06  0:15             ` John David Anglin
     [not found] ` <20121004051359.GA24664@ZenIV.linux.org.uk>
2012-10-04 10:02   ` James Bottomley
2012-10-04 12:22     ` Al Viro
2012-10-04 12:57       ` James Bottomley
2012-10-04 13:30         ` Carlos O'Donell
2012-10-04 14:07           ` Al Viro
2012-10-05  0:00             ` John David Anglin

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=1349776521.2615.54.camel@dabdike.int.hansenpartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-parisc@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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