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 CEE95ECAAA1 for ; Tue, 30 Aug 2022 17:25:28 +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=aa0JwsVTF8/Jdvoz1q710vehRt6lVHCpRU+nWaLJ950=; b=GJpZytqVoIUg7o AC9idJ5O7g+61Nd3J8zCVPku+JPI3oAp8IOPMsYBLzhzjd2wAEV/Z4PmXBtU+WCPVd1hxixulQ0HG +W2gURDAE/yJXsPp9av3POIT9i33PcQK0fUNJJZr1n9qDdFEoSjE1kxhZZeJtTbTTrGBA6Jn1I8sf M2NT5gYWHNf2oAnjzaJFj9UPtM6RYYRBObYvLXOxU+XXWfJpYKTjxwEfpsvur45K+i0CGlqhTwGUl 8bGWysbrgCoHznCDa+mDB0Lut/bUH5ct+FC/pjHUQbEI9jr9uL47wvye2HWadVitAIRym13f8R266 phbM2LAEzCwzBmVJKWAg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oT4yS-000oAd-Ru; Tue, 30 Aug 2022 17:24:29 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oT4yA-000o4K-76 for linux-arm-kernel@lists.infradead.org; Tue, 30 Aug 2022 17:24:12 +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 CE330B81D14; Tue, 30 Aug 2022 17:24:08 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 37291C433D7; Tue, 30 Aug 2022 17:24:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661880247; bh=HXfZo6doQzz9VapJaBP8Fx6rQF3F4A3r+CJnHaVGpWM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=cpZXTejoEmts2mk2oV7+gtKPftEB6vVTX0prtb6ZXg6plsR4xQIVmvKqWPJUGsdO5 GPO7WRWp8gVnQsBjGroLN3m0m06+ST3Fvg7nPgxYDM5Ugkb8wIGkBQEQsTUgtNNVJN i9vtCWeOd0c5tsiVkNtTe3P98OQxUfaRP+Jvk1VCmk/36OEXEV2KmE+LTuyzrq8k+Y hoTGVFofqskSg3bmXKNY0p10p8t8y3IbZytWUrL7dEgA71459JeYy55qFz79x/qshE xPlx7+HjXM+awJhj11WAnE/cTgDNmgIXguYmrjcw7r423x8yHAgz7dPSxtkuyLWSwd 5drqikev/xoGw== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Mark Brown , Catalin Marinas , Will Deacon , Sasha Levin , tglx@linutronix.de, ebiederm@xmission.com, seanjc@google.com, mark.rutland@arm.com, david.engraf@sysgo.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH AUTOSEL 5.10 11/16] arm64/signal: Raise limit on stack frames Date: Tue, 30 Aug 2022 13:23:12 -0400 Message-Id: <20220830172317.581397-11-sashal@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220830172317.581397-1-sashal@kernel.org> References: <20220830172317.581397-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_102410_446324_46E7AF39 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 0dab5679a97d5..c42089ce089f7 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