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 0CD65ECAAD8 for ; Tue, 30 Aug 2022 17:32:56 +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=YfeeDz9MeJhxGEnIylps50ELo5zw1wiAqdi86I/X1qE=; b=KzyFVoFYDquGNt oYReykxEWjkWbjmizNyOIFBtB1jf0Gd2eWYy5vEROzbglSp9xDGOFmdBXDThz5cTGhNeFFMNd20cV O7M0RJhNfVFmAksPl8wLGrmFJiOu3BjOdeuza5DfQAf66mbNnqc4BHCkvUw+MjdBSrwJR4poGzqxM gd+IalFeS3/YmVYPTpHsI5QGZrLZvbnDjr8k3k7k0kYZXpGy6sChvxreeZxGDefG2TgLvKu6uJuxA QIkIbF0PR0R+o8bMkeaNtcVOnPhq8ZzhnoZzTzjDWm4WujQN5VsE7pdDWox8AQOSI9JvPPlQ+LOsh 3nHPf1kB88hfUBaOQ+QA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oT55S-000rwW-7p; Tue, 30 Aug 2022 17:31:43 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oT50n-000pXe-Sg for linux-arm-kernel@lists.infradead.org; Tue, 30 Aug 2022 17:26:55 +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 dfw.source.kernel.org (Postfix) with ESMTPS id 66836617B7; Tue, 30 Aug 2022 17:26:53 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A9B71C433D6; Tue, 30 Aug 2022 17:26:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1661880412; bh=xdlYmvdwMdSGOG7QzbxeM1ku4krKuvDuV1ZgWmDgk1I=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=U4RhTE1F6zPlqKNLei4ISLPDAfIoo6w6RY6X6zlx2993laVYv02DpHSSSxxonJpKK TSMOMM492I++TBWx0a6UXwsdxi5xxiXudhHES+CWWZUGz5zsQuoUBNdrP2ZitfluxO 4Xi5+yv0LOAsWwUnWCUezDoPN9eJIutWFd13DlLo4MYN9U1rk1YJ4/92Mn84HrTR27 3KHKaVwjtDZFj6s03ZNDZm5norBeKcUawKCCXanj52WBi/r2hIv93Aty0Ik2Gb+0hR 8i7EsbkmvXxDUQcNJ8iWY9Y1c4BwQrBOk69iAsdJCCGLK2MEiHrcpJkmZ1EEpYaoAa pf5CQ3s5nLKEg== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Mark Brown , Catalin Marinas , Will Deacon , Sasha Levin , mark.rutland@arm.com, ebiederm@xmission.com, elver@google.com, seanjc@google.com, david.engraf@sysgo.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH AUTOSEL 4.14 6/8] arm64/signal: Raise limit on stack frames Date: Tue, 30 Aug 2022 13:26:29 -0400 Message-Id: <20220830172631.581969-6-sashal@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220830172631.581969-1-sashal@kernel.org> References: <20220830172631.581969-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_102654_002941_F607CFD5 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 43442b3a463f5..1b3973de417ec 100644 --- a/arch/arm64/kernel/signal.c +++ b/arch/arm64/kernel/signal.c @@ -97,7 +97,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