From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965055AbcFMHwR (ORCPT ); Mon, 13 Jun 2016 03:52:17 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:36710 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964901AbcFMHwO (ORCPT ); Mon, 13 Jun 2016 03:52:14 -0400 Date: Mon, 13 Jun 2016 08:52:10 +0100 From: Sudip Mukherjee To: Kees Cook Cc: Michal Marek , Stephen Rothwell , Emese Revfy , Paul Gortmaker , Linux-Next , linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com Subject: Re: [PATCH] gcc-plugins: disable under COMPILE_TEST Message-ID: <20160613075210.GB2031@sudip-tp> References: <20160611161212.GA29370@www.outflux.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160611161212.GA29370@www.outflux.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jun 11, 2016 at 09:12:12AM -0700, Kees Cook wrote: > Since adding the gcc plugin development headers is required for the > gcc plugin support, we should ease into this new kernel build dependency > more slowly. For now, disable the gcc plugins under COMPILE_TEST so that > all*config builds will skip it. But don't you think that people who are actually building the kernel with allmodconfig or allyesconfig and/or with COMPILE_TEST enabled are just doing that to build test the kernel. Atleast for me, when I am testing i will always do allmodconfig but when I am building which is to be deployed somewhere then I am building with a particular config. Regards Sudip