From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754901AbdFWTU2 (ORCPT ); Fri, 23 Jun 2017 15:20:28 -0400 Received: from mail-it0-f43.google.com ([209.85.214.43]:36936 "EHLO mail-it0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754327AbdFWTU1 (ORCPT ); Fri, 23 Jun 2017 15:20:27 -0400 MIME-Version: 1.0 In-Reply-To: <20170623140651.GD5314@dhcp22.suse.cz> References: <20170620230911.GA25238@beast> <20170623140651.GD5314@dhcp22.suse.cz> From: Kees Cook Date: Fri, 23 Jun 2017 12:20:25 -0700 X-Google-Sender-Auth: FD5MihmjBK3WGCFXl6PN6ceMfe8 Message-ID: Subject: Re: [PATCH v2] mm: Allow slab_nomerge to be set at build time To: Michal Hocko Cc: Christoph Lameter , Jonathan Corbet , Daniel Micay , David Windsor , Eric Biggers , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , "Rafael J. Wysocki" , Thomas Gleixner , Ingo Molnar , Mauro Carvalho Chehab , "Paul E. McKenney" , Arnd Bergmann , Andy Lutomirski , Nicolas Pitre , Tejun Heo , Daniel Mack , Sebastian Andrzej Siewior , Sergey Senozhatsky , Helge Deller , Rik van Riel , "linux-doc@vger.kernel.org" , Linux-MM , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 23, 2017 at 7:06 AM, Michal Hocko wrote: > On Tue 20-06-17 16:09:11, Kees Cook wrote: >> Some hardened environments want to build kernels with slab_nomerge >> already set (so that they do not depend on remembering to set the kernel >> command line option). This is desired to reduce the risk of kernel heap >> overflows being able to overwrite objects from merged caches and changes >> the requirements for cache layout control, increasing the difficulty of >> these attacks. By keeping caches unmerged, these kinds of exploits can >> usually only damage objects in the same cache (though the risk to metadata >> exploitation is unchanged). > > Do we really want to have a dedicated config for each hardening specific > kernel command line? I believe we have quite a lot of config options > already. Can we rather have a CONFIG_HARDENED_CMD_OPIONS and cover all > those defauls there instead? There's not been a lot of success with grouped Kconfigs in the past (e.g. CONFIG_EXPERIMENTAL), but one thing that has been suggested is a defconfig-like make target that would collect all the things together. I haven't had time for that, but that would let us group the various configs. Additionally, using something like CONFIG_CMDLINE seems a little clunky to me. -Kees -- Kees Cook Pixel Security