From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C1587C43387 for ; Sun, 13 Jan 2019 09:52:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 872CB20879 for ; Sun, 13 Jan 2019 09:52:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547373136; bh=3HRBbDaxAA+67iqYn+s23hVSgaGOVYPy2eoaj8kq8uA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=RxQ1Kda21OkNgUnuAiJhvVZuxPxOTAH9i0HgTQZ+RfdCISbnaGjkIoA41taJU5+zn 2LNZYAO5Qdn4Z6XvxKwshZCvqUaDq4DUpMvj/C0UpGrEdI3sUp50nj1ji0AZHJkbcW B6rCbZGUSIepR5dnPugddQvfPng3OKSUfQaUWPpQ= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726409AbfAMJwQ (ORCPT ); Sun, 13 Jan 2019 04:52:16 -0500 Received: from mail.kernel.org ([198.145.29.99]:47786 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725875AbfAMJwP (ORCPT ); Sun, 13 Jan 2019 04:52:15 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E6C2E20873; Sun, 13 Jan 2019 09:52:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547373135; bh=3HRBbDaxAA+67iqYn+s23hVSgaGOVYPy2eoaj8kq8uA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ITp6dO1Gafl0gIZ2pyKa+ypmsvGM8TFzTA2+lJXfXFLT8/l2xzZ3ozbbAoY1E6pAl F9eAermhcovBr0hulYSwkcZEkvp49YmgyNZf0wOB+ylyjmUHVEn7y5paie1JG6EukE h0x9UvpNfbQJswoAGJ1xkMJy+MDdxEf3z2/lT62E= Date: Sun, 13 Jan 2019 10:52:13 +0100 From: Greg Kroah-Hartman To: Guenter Roeck Cc: stable@vger.kernel.org, "David S. Miller" , Ben Hutchings Subject: Re: boot stalls when booting sparc32 images on v3.16.y/v3.18.y in qemu Message-ID: <20190113095213.GA12768@kroah.com> References: <20190111212635.GA6399@roeck-us.net> <20190111221558.GA3067@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190111221558.GA3067@roeck-us.net> User-Agent: Mutt/1.11.2 (2019-01-07) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Jan 11, 2019 at 02:15:58PM -0800, 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 > AuthorDate: Wed Nov 9 10:43:05 2016 +0100 > Commit: David S. Miller > CommitDate: Thu Nov 10 16:47:38 2016 -0800 > > sparc32: Fix inverted invalid_frame_pointer checks on sigreturns Now queued up, thanks. greg k-h