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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id DA50EECAAD1 for ; Tue, 30 Aug 2022 17:26:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=FZT64ALylx3r3KOvvKZqwWsD8lrC32NdKidRDK7SvMU=; b=FOJ37Z7CzcjhQg 5yjL502E3FF+FhYZJ/kg82C2K88leuko5QsMlwFRWgpHyxEhSAK8ngl8qzsH0aSPNI3H+ndXkd00f bzbkeDffvRCNJ85ySD6pzHc32KFW2VZ33PDNshyvONfkfXNi/6+bKYMDecnxofkocopRe60q+buEH kaQxE3pHUHdZDXYppJXssEiDov8hXbs7OUyMSlrqsBpd/d206tl07VuX61Ck+vtWy64nfjOXPs7lY y0404D5Y2DGi7PrMI4P9mRyqP2R/wjD8Kc12/E0NXTfmvyIkiQG3TL8zXfX8L0YVGi8Xn99s491OR 8HgLqFfNKaqeP0qgBL+w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oT4zl-000owz-FF; Tue, 30 Aug 2022 17:25:49 +0000 Received: from ams.source.kernel.org ([2604:1380:4601:e00::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oT4zL-000ojL-4l for linux-arm-kernel@lists.infradead.org; Tue, 30 Aug 2022 17:25:25 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id C663EB81D15; Tue, 30 Aug 2022 17:25:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 54710C433D7; Tue, 30 Aug 2022 17:25:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661880321; bh=sDaOvwr6YJekxpEPBn7NfFtwuiIo6HkgI8ymFIIvqUE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=kmqMOnbo8cH2Td30q5nwemWVoQUXE+xE8tcVYuuXjIm5l2NYb+uMcg+4J/ndrUPWz yTDnjl+J0fdggT5PhOBeHYkeXt+e/S97R1JHxlxgFgzjknblxiiTmDfWTE5QqeX/Kx OWerXrnFvxMiTKYsJketxMCpKg1V/5M7JGbwutYFAiU8ShRFZ3aNKij86jJrpcTd/5 uX4rnYaNnNA7ugNkrtBaL3cJB+aZNbW2vRdt1iuLhJDpuJiuTe1iAKQrMSRDM7wNFK 0O67GFTY0CSoWf6PYxxA0gHSpmgtHRuUHBUJpJVtZxExCxsiQpYhfIW74/Gcz0X9Xu wshIVlyAKd5rA== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Mark Brown , Catalin Marinas , Will Deacon , Sasha Levin , geert@linux-m68k.org, seanjc@google.com, david.engraf@sysgo.com, mark.rutland@arm.com, elver@google.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH AUTOSEL 5.4 09/12] arm64/signal: Raise limit on stack frames Date: Tue, 30 Aug 2022 13:24:40 -0400 Message-Id: <20220830172444.581654-9-sashal@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220830172444.581654-1-sashal@kernel.org> References: <20220830172444.581654-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220830_102523_416471_49371FBA X-CRM114-Status: GOOD ( 17.10 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org From: Mark Brown [ Upstream commit 7ddcaf78e93c9282b4d92184f511b4d5bee75355 ] The signal code has a limit of 64K on the size of a stack frame that it will generate, if this limit is exceeded then a process will be killed if it receives a signal. Unfortunately with the advent of SME this limit is too small - the maximum possible size of the ZA register alone is 64K. This is not an issue for practical systems at present but is easily seen using virtual platforms. Raise the limit to 256K, this is substantially more than could be used by any current architecture extension. Signed-off-by: Mark Brown Acked-by: Catalin Marinas Link: https://lore.kernel.org/r/20220817182324.638214-2-broonie@kernel.org Signed-off-by: Will Deacon Signed-off-by: Sasha Levin --- arch/arm64/kernel/signal.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/kernel/signal.c b/arch/arm64/kernel/signal.c index f6d3278c1a4e0..92afd44db9dd8 100644 --- a/arch/arm64/kernel/signal.c +++ b/arch/arm64/kernel/signal.c @@ -91,7 +91,7 @@ static size_t sigframe_size(struct rt_sigframe_user_layout const *user) * not taken into account. This limit is not a guarantee and is * NOT ABI. */ -#define SIGFRAME_MAXSZ SZ_64K +#define SIGFRAME_MAXSZ SZ_256K static int __sigframe_alloc(struct rt_sigframe_user_layout *user, unsigned long *offset, size_t size, bool extend) -- 2.35.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel