From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 522D3C64E8A for ; Mon, 30 Nov 2020 20:13:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F10802074A for ; Mon, 30 Nov 2020 20:13:37 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="wK3ShHoB" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729213AbgK3UNc (ORCPT ); Mon, 30 Nov 2020 15:13:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44938 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727936AbgK3UNb (ORCPT ); Mon, 30 Nov 2020 15:13:31 -0500 Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 32B6DC0613D3 for ; Mon, 30 Nov 2020 12:12:51 -0800 (PST) Received: by mail-pj1-x1030.google.com with SMTP id p21so386068pjv.0 for ; Mon, 30 Nov 2020 12:12:51 -0800 (PST) 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=xdK8+qkc2rtuVSy5z4KzKkg6o06W3+GbexGx9SBitVM=; b=wK3ShHoBqxgZvGL9tz2LsiHza2V8Qq+i1MrEAA82aXcHCURZHT48vMhRLfCutCkbbR tAGnm1mcR0StRiQCdYH9CLtC9NeL81DgDQyBCIoS5Hzm5YBTPEqXF34iGGbE2z91z/7E myw7BuRoKXDtncCCJqTZDw8Y4Y2rucIu5M2Km60H8Mzrq34xnoCKSZ6IAfYoTudcV+N6 CNX5glIymgl1eVnYSHqP8oldWqjXhIqds4IN5qgRNysQkRpvd8qqBG0z7M0BOxfTUFj8 b1LCYg1p4TftgKSKQMB2nE0H5NXPcorXOww8cIFLpg2R5uaO72Te+WHM9hd+JctzpyaI /IDA== 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=xdK8+qkc2rtuVSy5z4KzKkg6o06W3+GbexGx9SBitVM=; b=f3DSJSmRR5jDfUa6fGxaMCmAy8eKrU/wo1YoLesPduClXoNh+rrNaBRuAK5Zc3q4cH SRj4wBD8MR0YQsRGCnOItgfQv5MwJMrCo4k/Id4A2rZKjQIcLaFL/4NxX+Pebi7Nt1Lb CYyBoO5M60ablFc8/DbNUzinfqfw7xe32YWncztgqmc0uEGFj8UTrS2TTMk6nDAzEQ/v m8ZyYlwxEzbhcrk88Xm3dO+FJosYtAkprE/6YvLR/tkH++a/5XA1sgfwb+tHRUqbK6f4 S7b8AvmZjXruOlABv5WBqFevCq02iqPRpSz3MCcfbyxYIMJm0rTX/XOXyzg5uthjOVWD 2HNw== X-Gm-Message-State: AOAM530CquCrfzHVUVcijIfFYR2Ds2b7v5DzsLjcxvLHLhsXq7JMEHeK OjAMyBgtU+ZjfbML8kj3w63Vd/4X5Ojrn0BY92mPPA== X-Google-Smtp-Source: ABdhPJy2yJpznno2UNGOaFhGigmzH2+/QnBPutAyxmqWdT9JN+hxh1ZKo5pJKmX/+BSK3ZR5qbTSWgDkYkoKYx+uAHY= X-Received: by 2002:a17:90a:dc16:: with SMTP id i22mr654696pjv.32.1606767170547; Mon, 30 Nov 2020 12:12:50 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Nick Desaulniers Date: Mon, 30 Nov 2020 12:12:39 -0800 Message-ID: Subject: Re: [stable 4.9] PANIC: double fault, error_code: 0x0 - clang boot failed on x86_64 To: Greg Kroah-Hartman Cc: Naresh Kamboju , linux-stable , open list , lkft-triage@lists.linaro.org, Sasha Levin , clang-built-linux , x86@vger.kernel.org, Matthias Kaehlcke Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 25, 2020 at 10:38 PM Greg Kroah-Hartman wrote: > > Is the mainline 4.9 tree supposed to work with clang? I didn't think > that upstream effort started until 4.19 or so. (For historical records, separate from the initial bug report that started this thread) I consider 785f11aa595b ("kbuild: Add better clang cross build support") to be the starting point of a renewed effort to upstream clang support. 785f11aa595b landed in v4.12-rc1. I think most patches landed between there and 4.15 (would have been my guess). From there, support was backported to 4.14, 4.9, and 4.4 for x86_64 and aarch64. We still have CI coverage of those branches+arches with Clang today. Pixel 2 shipped with 4.4+clang, Pixel 3 and 3a with 4.9+clang, Pixel 4 and 4a with 4.14+clang. CrOS has also shipped clang built kernels since 4.4+. -- Thanks, ~Nick Desaulniers