From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751382AbdCQTFq (ORCPT ); Fri, 17 Mar 2017 15:05:46 -0400 Received: from mail-vk0-f53.google.com ([209.85.213.53]:35733 "EHLO mail-vk0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751150AbdCQTFn (ORCPT ); Fri, 17 Mar 2017 15:05:43 -0400 MIME-Version: 1.0 In-Reply-To: <20170317185720.5s7qa6hl233t24ag@pd.tnic> References: <20170317001520.85223-1-md@google.com> <20170317001520.85223-7-md@google.com> <20170317120837.pr74cv3xuj7qpoin@hirez.programming.kicks-ass.net> <20170317180350.63jjysejk2i6vkon@pd.tnic> <20170317185720.5s7qa6hl233t24ag@pd.tnic> From: Dmitry Vyukov Date: Fri, 17 Mar 2017 20:05:16 +0100 Message-ID: Subject: Re: [PATCH 6/7] md/raid10, LLVM: get rid of variable length array To: Borislav Petkov Cc: Alexander Potapenko , Peter Zijlstra , Michael Davidson , Michal Marek , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Herbert Xu , "David S. Miller" , Shaohua Li , Matthias Kaehlcke , "x86@kernel.org" , "open list:KERNEL BUILD + fi..." , LKML , linux-crypto@vger.kernel.org, linux-raid@vger.kernel.org, kbuild-all@01.org, Fengguang Wu 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, Mar 17, 2017 at 7:57 PM, Borislav Petkov wrote: > On Fri, Mar 17, 2017 at 07:47:33PM +0100, Dmitry Vyukov wrote: >> This problem is more general and is not specific to clang. It equally >> applies to different versions of gcc, different arches and different >> configs (namely, anything else than what a developer used for >> testing). > > I guess. We do carry a bunch of gcc workarounds along with the cc-* > macros in scripts/Kbuild.include. > >> A known, reasonably well working solution to this problem is >> a system of try bots that test patches before commit with different >> compilers/configs/archs. We already have such system in the form of >> 0-day bots. It would be useful to extend it with clang as soon as >> kernel builds. > > Has someone actually already talked to Fengguang about it? +Fengguang > Oh, and the stupid question: why the effort to build the kernel > with clang at all? Just because or are there some actual, palpable > advantages? On our side it is: - clang make it possible to implement KMSAN (dynamic detection of uses of uninit memory) - better code coverage for fuzzing - why simpler and faster development (e.g. we can port our user-space hardening technologies -- CFI and SafeStack) You can also find some reasons in the Why section of LLVM-Linux project: http://llvm.linuxfoundation.org/index.php/Main_Page