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: Fri, 05 Oct 2012 15:47:56 +0100 [thread overview]
Message-ID: <1349448476.3638.60.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <1349444664.3638.46.camel@dabdike.int.hansenpartnership.com>
On Fri, 2012-10-05 at 14:44 +0100, James Bottomley wrote:
> On Fri, 2012-10-05 at 12:07 +0100, James Bottomley wrote:
> > I tried out the code at
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal.git
> > experimental-kernel_thread
> >
> > and it gives me this panic on boot.
>
> OK, found the fix: the idle thread is a kernel thread, but it doesn't
> come through kernel_thread(). The fix is to check for it (fortunately
> it has the signal usp == 0).
>
> I'm now getting as freeing the init memory, which then hangs, so I
> suspect some type of execve failure trying to start the initrd... I'm
> debugging.
And the fix for this one is below: ret_from_kernel_execve has pt_regs in
%r26 ... it needs to be in %r16 for intr_return, so we just copy them
over.
With this, I can bring up the kernel all the way to a login prompt with
no apparent ill effects.
James
---
diff --git a/arch/parisc/kernel/entry.S b/arch/parisc/kernel/entry.S
index 272c7a0..dd137fc 100644
--- a/arch/parisc/kernel/entry.S
+++ b/arch/parisc/kernel/entry.S
@@ -744,7 +744,8 @@ ENDPROC(ret_from_kernel_thread)
ENTRY(ret_from_kernel_execve)
mfctl %cr30, %r1
ldo THREAD_SZ_ALGN(%r1), %r30
- b,n intr_return /* forward */
+ b intr_return /* forward */
+ copy %r26,%r16 /* pt_regs into r16 */
ENDPROC(ret_from_kernel_execve)
next prev parent reply other threads:[~2012-10-05 14:47 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 [this message]
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
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=1349448476.3638.60.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