From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932105AbdJJKfe (ORCPT ); Tue, 10 Oct 2017 06:35:34 -0400 Received: from ozlabs.org ([103.22.144.67]:32893 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756014AbdJJKfd (ORCPT ); Tue, 10 Oct 2017 06:35:33 -0400 From: Michael Ellerman To: Kees Cook , Christophe LEROY Cc: Balbir Singh , Benjamin Herrenschmidt , Paul Mackerras , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] powerpc: Default to enabling STRICT_KERNEL_RWX In-Reply-To: <20171005190317.GA98302@beast> References: <20171005190317.GA98302@beast> Date: Tue, 10 Oct 2017 21:35:30 +1100 Message-ID: <87infnwarx.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kees Cook writes: > When available, CONFIG_KERNEL_RWX should be default-enabled for PPC64. > On PPC32, there is a performance trade-off. Thanks for prodding us. But I think we need some more test cycles on this before we make it the default. As Balbir said it's currently not compatible with RELOCATABLE, which means most folks aren't enabling it. We also don't have good numbers on what the performance impact is on 64-bit. So although it almost certainly should be the default in future, I'd still like us to have some idea of what it's costing us. I'll try and get some perf numbers. cheers