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=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, 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 CE469C43387 for ; Fri, 11 Jan 2019 22:16:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9DD352084C for ; Fri, 11 Jan 2019 22:16:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="cO/c+G4R" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726476AbfAKWQC (ORCPT ); Fri, 11 Jan 2019 17:16:02 -0500 Received: from mail-pl1-f178.google.com ([209.85.214.178]:36549 "EHLO mail-pl1-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726474AbfAKWQB (ORCPT ); Fri, 11 Jan 2019 17:16:01 -0500 Received: by mail-pl1-f178.google.com with SMTP id g9so7355526plo.3 for ; Fri, 11 Jan 2019 14:16:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=6QXZ7F4o5yM08IKPZxSKoLu/ldS5gmpvThTk2FUSLEg=; b=cO/c+G4RsMu7msF8g+roIxj1U+Dyp2LXc22QxDxKKw/3RzP1kTbFdMO1dydwwa9gdh vE5x62+yGDmWbohGFtEAfucvagQVlO9xmk0gTlvnPyVFtydXPyMZxoEkBq6SL/gEVZBz fuO4SxizVClBWDzIpNt1t/78tXw1Ewp3WsyhXhCyyZ17b/KjSEsxIp4tCVvhjMj4yuhH ePDQwq+hYCSqjL/cvoXskAKCAL/OZOKdlsvOw9giR22Z6pBc3LGjthU5WzZROcjzNys7 wlVMhugZn3g/pB/MGScZqhBpQzA0jUbjaTwnAT1srwiwtFANR3a/NeUVfCZYVrhApqBA mWrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=6QXZ7F4o5yM08IKPZxSKoLu/ldS5gmpvThTk2FUSLEg=; b=fbTWFc/OXIuZxGsdALX2rOqZqFJ+hQVs74lgtjzvMO24Cew0qcXbt4TIS0ZQwZGvFY 5BClCIhsMr1RipoYkFb45dgOIFwsuNkxtFv23PilxTRRlu/uChLKVctdimg83IhkDYAQ hzWOYCW1HtV5dsEtUs7Tv+ODuL/m+FOnS/+G6bvZIsa6MMqmCLoNiXloyhrYAxTXuwxv TnW40ygp17SzJu78M43woGw76N8w2rfYXcQjmSO9em5AWTJh3clPpU7cpWAcmA4MBq1B cnsVoadVECZ3twHqA8rNRVL0d4O0Si1I0q/wf380LAWK8RNcBUiqRCVJWwrAOmOAjCHs TLaQ== X-Gm-Message-State: AJcUukek+9V+QLllnYfZpDfefGZlL3vOidA9t1LRhWsGA2G7FQ6/GIwN EJ251GHYK7dSpo93Pa++HZi5lKvb X-Google-Smtp-Source: ALg8bN55yJIMKJZd0wlNMPqMpH1AcfhqNvDkGvAEGoHIYxOwWcATqCd/HppQJaYxtpReI2dwJWYb0g== X-Received: by 2002:a17:902:9a07:: with SMTP id v7mr15912014plp.247.1547244960850; Fri, 11 Jan 2019 14:16:00 -0800 (PST) Received: from localhost ([2600:1700:e321:62f0:329c:23ff:fee3:9d7c]) by smtp.gmail.com with ESMTPSA id k15sm136000202pfb.147.2019.01.11.14.15.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Jan 2019 14:15:59 -0800 (PST) Date: Fri, 11 Jan 2019 14:15:58 -0800 From: Guenter Roeck To: stable@vger.kernel.org Cc: "David S. Miller" , Greg Kroah-Hartman , Ben Hutchings Subject: Re: boot stalls when booting sparc32 images on v3.16.y/v3.18.y in qemu Message-ID: <20190111221558.GA3067@roeck-us.net> References: <20190111212635.GA6399@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190111212635.GA6399@roeck-us.net> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 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 Guenter