From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Vyukov Subject: Re: [PATCH 6/7] md/raid10, LLVM: get rid of variable length array Date: Fri, 24 Mar 2017 14:50:24 +0100 Message-ID: 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> <20170317192642.qnrf7xuopxzapl2r@hirez.programming.kicks-ass.net> <20170317192935.d5almj4brat6uvlt@hirez.programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Borislav Petkov , Alexander Potapenko , 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 To: Peter Zijlstra Return-path: In-Reply-To: <20170317192935.d5almj4brat6uvlt@hirez.programming.kicks-ass.net> Sender: linux-kbuild-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Fri, Mar 17, 2017 at 8:29 PM, Peter Zijlstra wrote: > On Fri, Mar 17, 2017 at 08:26:42PM +0100, Peter Zijlstra wrote: >> On Fri, Mar 17, 2017 at 08:05:16PM +0100, Dmitry Vyukov wrote: >> > You can also find some reasons in the Why section of LLVM-Linux project: >> > http://llvm.linuxfoundation.org/index.php/Main_Page >> >> From that: >> >> - LLVM/Clang is a fast moving project with many things fixed quickly >> and features added. >> >> So what's the deal with that 5 year old bug you want us to work around? >> >> Also, clang doesn't support asm cc flags output and a few other >> extensions last time I checked. >> > > Another great one: > > - BSD License (some people prefer this license to the GPL) > > Seems a very weak argument to make when talking about the Linux Kernel > which is very explicitly GPLv2 (and not later). OK, I guess should not have referenced the llvm-linux page. So here are reasons on our side that I am ready to vouch: - 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) Michael is on a different team and has own reasons to do this.