stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: stable@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ben Hutchings <ben.hutchings@codethink.co.uk>
Subject: Re: boot stalls when booting sparc32 images on v3.16.y/v3.18.y in qemu
Date: Fri, 11 Jan 2019 14:15:58 -0800	[thread overview]
Message-ID: <20190111221558.GA3067@roeck-us.net> (raw)
In-Reply-To: <20190111212635.GA6399@roeck-us.net>

On Fri, Jan 11, 2019 at 01:26:35PM -0800, Guenter Roeck wrote:
> Hi,
> 
> I recently updated the sparc32 root file system in my testbed
> with one generated with buildroot.
> 
> As a result, sparc32 images no longer boot with v3.16.y and v3.18.y.
> The system starts to come up, but stalls while starting syslog.
> However, v3.16 and v3.18 do boot.
> 
> I bisected v3.18.y and ended up with commit 16c193364b4 ("sparc: Harden
> signal return frame checks.") as culprit; bisect results below. Reverting
> this commit fixes the problem for both v3.16.y and v3.18.y.
> 
> Is it worth spending any time on this, or should I just stop testing
> sparc32 boot tests with v3.16.y and v3.18.y ?
> 

After some more digging ... here is the quite obvious fix:

commit 07b5ab3f71d318e52c18cc3b73c1d44c908aacfa
Author:     Andreas Larsson <andreas@gaisler.com>
AuthorDate: Wed Nov 9 10:43:05 2016 +0100
Commit:     David S. Miller <davem@davemloft.net>
CommitDate: Thu Nov 10 16:47:38 2016 -0800

    sparc32: Fix inverted invalid_frame_pointer checks on sigreturns

Guenter

  reply	other threads:[~2019-01-11 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 21:26 boot stalls when booting sparc32 images on v3.16.y/v3.18.y in qemu Guenter Roeck
2019-01-11 22:15 ` Guenter Roeck [this message]
2019-01-13  9:52   ` Greg Kroah-Hartman
2019-01-15 23:51   ` Ben Hutchings

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=20190111221558.GA3067@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@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 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).