Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752093AbeACN56 (ORCPT + 1 other); Wed, 3 Jan 2018 08:57:58 -0500 Received: from mail-it0-f67.google.com ([209.85.214.67]:44171 "EHLO mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751571AbeACN55 (ORCPT ); Wed, 3 Jan 2018 08:57:57 -0500 X-Google-Smtp-Source: ACJfBoufU/Bxt+boM2PgbTtM0gjZJn+R0+b6Vbaf9+M1MxbIBwGuMULUTS3dH4siRino2wDqopWwLsOG07RHwiVN3FQ= MIME-Version: 1.0 In-Reply-To: References: <20171221075036.GA32158@pjb1027-Latitude-E5410> From: Ard Biesheuvel Date: Wed, 3 Jan 2018 13:57:55 +0000 Message-ID: Subject: Re: [kernel-hardening] [PATCH] arm: kernel: implement fast refcount checking To: Jinbum Park Cc: Dave Martin , linux-arm-kernel@lists.infradead.org, LKML , Kernel Hardening , Russell King , Will Deacon , Peter Zijlstra , boqun.feng@gmail.com, Ingo Molnar , Mark Rutland , Nicolas Pitre , mickael.guene@st.com, Kees Cook , Laura Abbott Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 3 January 2018 at 13:36, Jinbum Park wrote: >>> This is a nice result. However, without any insight into the presence >>> of actual refcount hot spots, it is not obvious that we need this >>> patch. This is the reason we ended up enabling CONFIG_REFCOUNT_FULL >>> for arm64. I will let others comment on whether we want this patch in >>> the first place, > > Dear Ard, Dave, > > I wanna hear some comment on above point. > Is CONFIG_REFCOUNT_FULL much better for arm? > If it is, I don't need to prepare v2 patch. (then, just needed to add > "select REFCOUNT_FULL") > Well, we should probably turn that around. Please use REFCOUNT_FULL, until you run into a use case where the slowdown is noticeable. If nobody ever notices, we don't need to fix anything.