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 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 000F5ECAAD1 for ; Tue, 30 Aug 2022 17:23:52 +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=vnnKo7lY2VNizY2sWy0+yivZ7eqH7eCZrFT38s5jJ50=; b=2Sz9Z/leAGLlmJ 3QIV2ahky23ne/gsnOzWAEVOAvtnj+LrlayxIQgzCsSDAPcv5TjkTFclphnMpQ/4lAVINJ1DLu4QC 2YwSI6mPVXZR9latmx7gMNVvWi1x6oMf/ThxtAKIPiQMbLynDU/bxiZpXhcnE/ZVdQ5k5AOPTdFXo OE3c/xnzf1IunL4NXSGeX2+XCm/rZd9qs4AJ+VzBcL6TjqYPPoCBIJ1wAn60T9z7LDWnN3EbsiIce 6g2L7UtSZj7y7BGG1EvsUi9E2dOVMu21HomIlw94NDlcxs88/uuSmTauIBmERnNRRNXpZ2DSNd1uk cEUN92znFgCPAfTPA02A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oT4wx-000nLQ-GE; Tue, 30 Aug 2022 17:22:55 +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 1oT4wi-000nEZ-CB for linux-arm-kernel@lists.infradead.org; Tue, 30 Aug 2022 17:22:42 +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 17179B81D17; Tue, 30 Aug 2022 17:22:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B0D8EC433D6; Tue, 30 Aug 2022 17:22:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661880157; bh=jOv8v60wKjLg//lVQgOMfjenwYCSv7sZQmxfzg2d6BU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=MVGgHtZxJkMGG4w8RGQOlsQlY8SLmZ22IJ6t8Se68uQLKYiyedw9Us7IlZhpdz14x GpHSjDS6ugXJyKWKn1PC3CIv9qC8+j4eFYrbzad6sOKp1smZGlNNNPAlTjA/2r1pra GjNlpgsx/VE1dHBmnb1i+hncPvStdDEM+o43hpvroGtBBclGXSy+3OSb52T1BpTGv6 4LBOWC+H0C93YHGzS2CMR4YJqV4s0LxDRrblnTmG5lr0S8t5LI1GKnd90557FM7+Vn sWQBMN7AYlx2alCyqeEgshxlOzl2JLHrDi0M3KFuIHrxk+UyO8To1bWCNAga+vduaS htvVpy4k9YghQ== 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, mark.rutland@arm.com, elver@google.com, david.engraf@sysgo.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH AUTOSEL 5.15 14/23] arm64/signal: Raise limit on stack frames Date: Tue, 30 Aug 2022 13:21:31 -0400 Message-Id: <20220830172141.581086-14-sashal@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220830172141.581086-1-sashal@kernel.org> References: <20220830172141.581086-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_102240_586591_A66DB2C7 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 b3e1beccf4588..8fdb89afd2b85 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