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 E0094ECAAD1 for ; Tue, 30 Aug 2022 17:21:40 +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=j7ClXDx1oKFaT3bLI/szgADNZCxRPmwOp7yXm9vg6zo=; b=aumxfTcS2I6wmg IvX/n+3ahnGGEpM6/GzTJ4vNZ6X3JsZRY4mOZ2x78TkPhOBs3O7cRzZhkMfpqTZgnEWY24TtGIPKp uyu4P2KopzoNnI07/nlz5oosw++DxZu4OVKEHIl5ljf8quYWV1WNk8O3Qdi/kKiFxg5wVqJ0xZ8A3 DnyaMi9JmyrNgl6I2WuRfmb9zfbrJMcUfW3rEA4xH/zuLtVzh4cbISwnQVwN1RJVZEOFEG6P2nqmN 1Ru/TnfgdFqHYpLhhRBgRCqrVLK0ojUfCMwUHwTMyrHpdNONO8J9mvzji0oD743swI7URHCA4nw6A HjcRJT4HYXkpsFAidSQQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oT4us-000m9l-GB; Tue, 30 Aug 2022 17:20:46 +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 1oT4uV-000lz2-Rw for linux-arm-kernel@lists.infradead.org; Tue, 30 Aug 2022 17:20: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 8CBC0B81D0B; Tue, 30 Aug 2022 17:20:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 02D8FC433C1; Tue, 30 Aug 2022 17:20:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661880021; bh=qmmHo+XCKyEvqzJMxMcUvhPV//az47qcZ/1JnpnPPMc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=EfFWpjCGG2p919UENd294qWKLL92kaTNnQ5M6v78ZBr5w7BEQ7tg97qzaWi4buKjE Ze5g6YkQdKGkVzIFFfHBHe8kELQ28wZXUGRwBUD7UcxsTTzoKSIPAP1ADveSkUHIIS 7cvP5rxdeQ80VlS3LyyYOtbUgWbc0/SYgnCqXqJCgnnmm6J+zrLvrIGPU30DPoPSwB 5xdwJB6VoSB3BaDVKijQD7J3RuDtG3eKjsiJ4kw+ZgdZ8NQzTOYzS1EWqFxeGZ2ix0 s5WLbRHPCKjRsXrOAQXv0wfscBcb5HfjGmZc9kE7e3nJfupG2aOLda0glmyd0l32BH 46WpuEhhhmVhA== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Mark Brown , Catalin Marinas , Will Deacon , Sasha Levin , seanjc@google.com, pbonzini@redhat.com, ebiederm@xmission.com, mark.rutland@arm.com, elver@google.com, david.engraf@sysgo.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH AUTOSEL 5.19 20/33] arm64/signal: Raise limit on stack frames Date: Tue, 30 Aug 2022 13:18:11 -0400 Message-Id: <20220830171825.580603-20-sashal@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220830171825.580603-1-sashal@kernel.org> References: <20220830171825.580603-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_102024_073446_20E2412C X-CRM114-Status: GOOD ( 17.21 ) 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 b0980fbb6bc7f..118cc652468ff 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