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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B4CD3C77B73 for ; Sat, 6 May 2023 09:36:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231830AbjEFJgE (ORCPT ); Sat, 6 May 2023 05:36:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55478 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231450AbjEFJgD (ORCPT ); Sat, 6 May 2023 05:36:03 -0400 Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA8B39ECE; Sat, 6 May 2023 02:36:02 -0700 (PDT) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 5EA435C005F; Sat, 6 May 2023 05:35:58 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sat, 06 May 2023 05:35:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1683365758; x=1683452158; bh=W hKrTyJEAyCUMMB5cfUBewlKxI58jwdpn9YfS92b3dg=; b=eRVxFphIXwdZFLUPn jPwJO2ZGYXT5eYs4OY9zaHTe9HSnOA7quCC6hGUEUgLslui+BScbR27DQRkPD+JT zrKs1nmT6vriAgPC6ozklipykcCw2FObu1DQ2ldBCRcHlrkEQqPrPpktO+WgwFVs O9VxxLY1wuBjlyFaHqra+2Asm1SjB0bZrnPkyjTFR6A5+Fy8qUE85dRCx2j6yVZk 7vm7qCnz+38u5vovV4DPmfJrNSfLptha2b98sy9lf9THpu5x29p80kZf52Vpq1ZK peZCKc2qx14rvldz9sFWEPvJYn46g/YjidPplqjlbfGFFivtGShebFbDv5NRNG+i Af+tw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeeffedgudegjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkhffufffvveestddtredttddttdenucfhrhhomhephfhinhhnucfvhhgr ihhnuceofhhthhgrihhnsehlihhnuhigqdhmieekkhdrohhrgheqnecuggftrfgrthhtvg hrnhepheffudekteffudetvdffffehgedtteekkeefvefgieethfevvddtlefhuddutedt necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepfhhthh grihhnsehlihhnuhigqdhmieekkhdrohhrgh X-ME-Proxy: Feedback-ID: i58a146ae:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 6 May 2023 05:35:56 -0400 (EDT) Message-Id: From: Finn Thain Subject: [PATCH v1 0/1] 68020/030 signal handling following exceptions Date: Sat, 06 May 2023 19:38:12 +1000 To: Geert Uytterhoeven Cc: linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org, "Michael Schmitz" , "Andreas Schwab" , stable@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org This patch prevents potential stack corruption on 68020/030 when delivering signals following a bus error or (theoretically) an address error. Changed since RFC: - Dropped patch 1 because, as Andreas pointed out, it will not work properly. Finn Thain (1): m68k: Move signal frame following exception on 68020/030 arch/m68k/kernel/signal.c | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) -- 2.37.5