Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp113548ybm; Tue, 26 May 2020 12:07:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyWkFpOYMgWQZccENbkoGy46/torO8OoFLVt9l2MvQnmLZWUFC4uy130LTU20hzn0pg/wiT X-Received: by 2002:a50:f182:: with SMTP id x2mr21397553edl.336.1590520028552; Tue, 26 May 2020 12:07:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590520028; cv=none; d=google.com; s=arc-20160816; b=OQ50zeW7NR08MSKvm/cef02c8XDblw1m9PIvZSI46sxX16UE+eGS8i7d5PW6d4kbu6 3D78TLNiYSi57Rum19XkvMUzdHeCJyD06iTCMZ83YabFvd3HLi4/Vz2HJwMaQc0k91xm CyHk4ad1Zhw6n8L//k+oIW3q2cQET8qycW9HIZTMOPwc+1jnfp7qgGVHa0HsPXcZXfg9 05foMxKxfyPBMgXUBJXowIkGAnFsB4wd47FHMmu7wTVp+8Y7fXwYSdEHbO2T1n02eOoa oMlbLZSPlbDUgW5k+9ktYRZEBOIeoA18RDnofT8tJKgO2wHHDn1K/TNpfgK6hAG7GSB8 /a2Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=4sUPSgvv9edvLPIOc2t/4H8nbTJaJkYNsphnA2ZqfEk=; b=uwARCvwbe6urSlQFL//OPHKkqiADJ4ojwBO2DaHqn5MtH6p2dlsQfqkGE1fXMxGKWY OxIjpRX0IOO02pMC67yUDTdXnZ1CQThOnijKU/5XpCx3ILsL21Gt1HNDp49P7As52kq4 OSSl3BMvt2NUREvn5PzAKjyVbwP6ZNaurIyH7Y7NgCntY9/aRKyxsSauuoBdW2K9oL8I P1bb4f1akS6vHMgd2317Mc976C7B/06b32BkKLL1n4sL1LZWckUaFf8vxhrgn4bZbUq9 YaHu4OB3hKk04JiT4IJfLRgmP44aySctYfyrQsZNjjfZgsZO4TNAyoFkmYDGgzBef+hp AWtg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=JXloKKSF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t8si394282ejs.266.2020.05.26.12.06.40; Tue, 26 May 2020 12:07:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=JXloKKSF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2403799AbgEZTBm (ORCPT + 99 others); Tue, 26 May 2020 15:01:42 -0400 Received: from mail.kernel.org ([198.145.29.99]:55998 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2403769AbgEZTBh (ORCPT ); Tue, 26 May 2020 15:01:37 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E31FB20849; Tue, 26 May 2020 19:01:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590519696; bh=il/4o51wW092OuGEyB1YyPj7Iaz57uDjzAjl7G8Mr48=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=JXloKKSF3Ez7mLaD0jIvkq7VFzJQ2k0yFIoiyWtUgvkkPzG/W049SRA+YOeC9k6qU ZQFEvq2scXMybfB6cPLOPgj7TPpe2xsGm4V+YmyFDihuqV08DfOwA/tnhMjX9gY2/c 1XpeeF6Kpjd0fCi3maJ/8S7derfyIIAnwL2nI+h0= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Michael Ellerman , Sasha Levin Subject: [PATCH 4.14 41/59] powerpc/64s: Disable STRICT_KERNEL_RWX Date: Tue, 26 May 2020 20:53:26 +0200 Message-Id: <20200526183920.506643993@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200526183907.123822792@linuxfoundation.org> References: <20200526183907.123822792@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Michael Ellerman [ Upstream commit 8659a0e0efdd975c73355dbc033f79ba3b31e82c ] Several strange crashes have been eventually traced back to STRICT_KERNEL_RWX and its interaction with code patching. Various paths in our ftrace, kprobes and other patching code need to be hardened against patching failures, otherwise we can end up running with partially/incorrectly patched ftrace paths, kprobes or jump labels, which can then cause strange crashes. Although fixes for those are in development, they're not -rc material. There also seem to be problems with the underlying strict RWX logic, which needs further debugging. So for now disable STRICT_KERNEL_RWX on 64-bit to prevent people from enabling the option and tripping over the bugs. Fixes: 1e0fc9d1eb2b ("powerpc/Kconfig: Enable STRICT_KERNEL_RWX for some configs") Cc: stable@vger.kernel.org # v4.13+ Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200520133605.972649-1-mpe@ellerman.id.au Signed-off-by: Sasha Levin --- arch/powerpc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig index b74c3a68c0ad..679e1e3c1695 100644 --- a/arch/powerpc/Kconfig +++ b/arch/powerpc/Kconfig @@ -141,7 +141,7 @@ config PPC select ARCH_HAS_GCOV_PROFILE_ALL select ARCH_HAS_SCALED_CPUTIME if VIRT_CPU_ACCOUNTING_NATIVE select ARCH_HAS_SG_CHAIN - select ARCH_HAS_STRICT_KERNEL_RWX if ((PPC_BOOK3S_64 || PPC32) && !HIBERNATION) + select ARCH_HAS_STRICT_KERNEL_RWX if (PPC32 && !HIBERNATION) select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST select ARCH_HAS_UBSAN_SANITIZE_ALL select ARCH_HAS_ZONE_DEVICE if PPC_BOOK3S_64 -- 2.25.1