On Mon, 2019-01-14 at 15:15 +0000, Guenter Roeck wrote:
> 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@xxxxxxxxxxx>
> AuthorDate: Wed Nov 9 10:43:05 2016 +0100
> Commit: David S. Miller <davem@xxxxxxxxxxxxx>
> CommitDate: Thu Nov 10 16:47:38 2016 -0800
>
> sparc32: Fix inverted invalid_frame_pointer checks on sigreturns
Thanks, I've queued this up for 3.16.
Ben.
--
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.
Attachment:
signature.asc
Description: This is a digitally signed message part
