linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: "Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH] powerpc/64e: Don't place the stack beyond TASK_SIZE
Date: Mon, 08 May 2017 10:52:37 -0500	[thread overview]
Message-ID: <1494258757.3694.1.camel@buserror.net> (raw)
In-Reply-To: <87zien7841.fsf@concordia.ellerman.id.au>

On Tue, 2017-05-09 at 00:09 +1000, Michael Ellerman wrote:
> Scott Wood <oss@buserror.net> writes:
> 
> > Commit f4ea6dcb08ea ("powerpc/mm: Enable mappings above 128TB") increased
> > the task size on book3s, and introduced a mechanism to dynamically
> > control whether a task uses these larger addresses.  While the change to
> > the task size itself was ifdef-protected to only apply on book3s, the
> > change to STACK_TOP_USER64 was not.  On book3e, this had the effect of
> > trying to use addresses up to 128TiB for the stack despite a 64TiB task
> > size limit -- which broke 64-bit userspace producing the following errors:
> > 
> > Starting init: /sbin/init exists but couldn't execute it (error -14)
> > Starting init: /bin/sh exists but couldn't execute it (error -14)
> > Kernel panic - not syncing: No working init found.  Try passing init=
> > option to kernel. See Linux Documentation/admin-guide/init.rst for
> > guidance.
> 
> For some reason I am not seeing this on my p5020ds?
> 
> I just checked, it's definitely booting:
> 
>   [    0.000000] Linux version 4.11.0-gcc5-g13e0988 (kerkins@alpine1-p1)
> (gcc version 5.2.1 20151001 (GCC) ) #1 SMP Mon May 8 05:33:22 AEST 2017
>   [    0.000000] Using CoreNet Generic machine description
>   ...
>   [    3.216940] systemd[1]: Detected architecture ppc64.
>   ...
>   Debian GNU/Linux stretch/sid p5020ds ttyS0
>   
>   p5020ds login:
> 
> 
> Anyway patch looks good, I'll pull it in with the rest of your tree.

Are you using a 64-bit userspace?

-Scott

  reply	other threads:[~2017-05-08 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  6:31 [PATCH] powerpc/64e: Don't place the stack beyond TASK_SIZE Scott Wood
2017-05-08 14:09 ` Michael Ellerman
2017-05-08 15:52   ` Scott Wood [this message]
2017-05-09 21:13     ` Michael Ellerman

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=1494258757.3694.1.camel@buserror.net \
    --to=oss@buserror.net \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).