Received: by 10.213.65.68 with SMTP id h4csp949938imn; Wed, 4 Apr 2018 09:56:03 -0700 (PDT) X-Google-Smtp-Source: AIpwx49842b53EDhaVTeJZlnVCxvHhbhMLqH7UdMpRt7Ly+JK5Ffz+2Q+Xa0hlXlFJ0x2x7jzLrd X-Received: by 2002:a17:902:7042:: with SMTP id h2-v6mr18889197plt.370.1522860963599; Wed, 04 Apr 2018 09:56:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522860963; cv=none; d=google.com; s=arc-20160816; b=lx/dunctFjSROtePcrOM/rFStSJMg3NwdpKgzwE3HhsCh1uwS+eywp0hcD8DpyRSWv pjnIR/CXH4oBZhezM2mLKxVH+ItKLQsZghxK0cVBCojmQWjNEIviHvtYFisoaQv2BP6r ySMwOhEvwEkXHiHVDo5w1CaWdL08GT2RwBCwYoRPC8Blzne6yecmiJwN9UZOp2MrJ6hN X5TorMRCb42s9Qy7bLJHVv0u/rJwtxIwm82kF1cIDDsnaoUaJr2JCNp+bY+xBlKtiCq4 Cb79/vaYs+sINahrsnwRSHOeTUM32wyidyFF7a/LZybuGOnCtNWGuujgVHWD3ui/L6Js 9xQA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature :arc-authentication-results; bh=q6g8+gS9hkGxO5S3hqh+RkyeYEYTG2JqBKvhicSbeiM=; b=F0pHm54C4WYraUUaDCeqd9/4NiW7/Rhy05CR5/lEa8GFQt8ev5MJGZWecfJDjzKbTY bOJN2lLN/HHy0vJ3CFZe7h7c6UXV1OxYPV6eESQoAB5jndAQ75XZ18NOEGG0anVkTBGC 9wCofISybKJJV+D4fLU/L9s6wmOXR8tAvpdP0QFZWzkOKW514/XTrrBHKgLByPs6+GS6 k7o/P1aaYRG02WpovY6pRqWkqm1e7BIe3XEQQzqeY7dAgCkFVVIPI0F5ww4JwMUz5XMN Dufx3yQEwnG3ZL/U3nkTK1Avm+zrJSs7ZibvD6WaAubs5QJlYFQtYS6EHShp/RHC0Od7 tlbw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=kayWLYte; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s1-v6si3343272plr.109.2018.04.04.09.55.49; Wed, 04 Apr 2018 09:56:03 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=kayWLYte; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752603AbeDDQyF (ORCPT + 99 others); Wed, 4 Apr 2018 12:54:05 -0400 Received: from mail-io0-f171.google.com ([209.85.223.171]:38643 "EHLO mail-io0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752466AbeDDQyD (ORCPT ); Wed, 4 Apr 2018 12:54:03 -0400 Received: by mail-io0-f171.google.com with SMTP id b20so27163152iof.5 for ; Wed, 04 Apr 2018 09:54:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q6g8+gS9hkGxO5S3hqh+RkyeYEYTG2JqBKvhicSbeiM=; b=kayWLYteEcHYbKRPI7kwObcKZFHd/4BQ9NE+73PD49a0m3B+QY7383QG7PfcxjeJrF CEhTX+UPkj8Rx1s2TPwFAwKdUQv6pWSJIhd8Rpgl569iKJuLAlUrO5QAOUWLbOZNdXj9 7nKxnIubvYeTJ+WTrTzna9H7DTrk0hegNJDu5k9ufMjIq/nXN3yI7OuyixmoUs1r1Yks vAjfljj++gAj5KSKdnxxmjCx3DtvtWkU9zRDZH8tdKNn9LkKkY4m4KUEsJXQBkjKDzM7 YNuIOSJ+HP+GWtBawo5NpW2hwwiYHKDHjZTCrFNI3fT9jAWUS7o6f0aLtXz+pDE0BbGH ETfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q6g8+gS9hkGxO5S3hqh+RkyeYEYTG2JqBKvhicSbeiM=; b=RTWfyj+GStUf4KtaK2OXpn7lQVea8hRMTqHkb98KS17AslSzHePp7c8AUM5oMbtK5f VBRmacFlEYP8W1KQgv1X38MC/qUxRUmZByIFie5bSVBnwiI4eS6+qblGbnTLOWR9ltA+ eyw8O2OF5AOiX9EEE7xZsGkBsgC3rXJJAAlfkBv1yn1Q0nU9ZdP6Qpw1GthyvrXh8bgG IgxVz1P/pJaGiBKybPb6CGEWUkrySFWbAWB38FgPoqm2PnHgaCImWEsa4Aoss0j3Lejv 05PQlpNZB0YlO57XOZxYZFK3bSqND6n9nXEMI1MVsCb8FM20mMPoTho33FBQFG+6JvJe lw8w== X-Gm-Message-State: AElRT7GWlM1QJ21mOE9w350kfx6FXApFCpCSSrB03p5f7VdquKhczVcl g2FC0HvmkwZ48xnKEU51WkpTl0HviiurK6bA0CWQ6w== X-Received: by 10.107.182.214 with SMTP id g205mr18328328iof.203.1522860842629; Wed, 04 Apr 2018 09:54:02 -0700 (PDT) MIME-Version: 1.0 References: <20180402095033.nfzcrmxvpm46dhbl@gmail.com> <20180403085904.GY4082@hirez.programming.kicks-ass.net> <20180403095118.rpf7tj577dppvx7d@gmail.com> <20180403180658.GE87376@google.com> <20180404093823.GC25996@kroah.com> In-Reply-To: <20180404093823.GC25996@kroah.com> From: Nick Desaulniers Date: Wed, 04 Apr 2018 16:53:52 +0000 Message-ID: Subject: Re: [GIT PULL] x86/build changes for v4.17 To: Greg KH Cc: Matthias Kaehlcke , Ingo Molnar , Peter Zijlstra , Linus Torvalds , LKML , Thomas Gleixner , Andrew Morton , James Y Knight , Chandler Carruth , Stephen Hines , Kees Cook , groeck@chromium.org, Greg Hackmann Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (re-sending as plain text) On Wed, Apr 4, 2018 at 2:38 AM Greg KH wrote: > There are known-bugs with building a kernel with clang right now (I > pointed one out a few days ago about NULL checks being deleted from the > clang output for no good reason, which really is scary for obvious > reasons). Is this the thread you are referring to? https://lkml.org/lkml/2018/3/27/1286 It's definitely something curious that I'll need to sit down and investigate more. If there are other known instances, it would be good to let me know. > So while it is great that small subsets of the kernel can > work properly (or hopefully properly), with clang, it still isn't ready > to be considered a "fully supported and we can't change the kernel if we > break using it" option, sorry. > And don't tie _anything_ to a LTS kernel, that's exactly what those > kernels are NOT for. You implement features and things in the kernel > when they are ready, and I'll pick a random LTS kernel out of the air > when I feel like it. Never should the two intersect and matter. > So please, work on fixing up clang for asm-goto and other "features" > that the kernel requires, and maybe when all build options/configs are > really solid and working well, will we be able to properly consider it > as a reason to implement, or not implement, something in the kernel > source. Acknowledged. -- Thanks, ~Nick Desaulniers