Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp399790pxu; Tue, 1 Dec 2020 14:16:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJw1k/QnuXq2/SKCNLh1oj+puYTa/MD99oOd9RSX2xPgiq4HitLoLajqxHhcXR+MrePr26fA X-Received: by 2002:a17:906:2798:: with SMTP id j24mr5193001ejc.328.1606861005211; Tue, 01 Dec 2020 14:16:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606861005; cv=none; d=google.com; s=arc-20160816; b=p8dUVkBVRPAUiIk/zY8bn5XFdnIV7BpPWEcbi+L3E8eYnh1S7DjNVpDGOdWc/xJPlO /bgTvCyzMFWchGNIRh1OHtnU+UikYmCdIZ8eDjTxAbr7UZBI78RNfJXts5sCGerX4wXT CWDoSDkjhLioXyhN77bUGaXE45G0qveI3NSZe+VtrZm05UGM3xmvEBi9Uda3oHxy+Xug OZQrK2c2UQ8f0y+N/GIRwW92s/t+GCzS8q3cozCfBG913ACfQmeMd3bawvdtq8lpIvAz Yb+XKj2KAvLdolieFiq716GUr75md3rQOeRMRpOhcY5Bw0WaICTGadMz2Y1NRHxO9n/7 mLlw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=slgr3MU9J18/tR1L03swMDktgNg3nfkGSTkXEJ2IjEE=; b=F/HB/Y5pMv/NmjkzK+TFJBSEzTi+280AURmlZyTL2jnTRerRXWAdvTgEA3S3xEo6kV eOilPZsxEAtp1MyZ6izZAtqX79kE7mRO6R4iCxWxWDshurhg+Dt9CEGo0nLZp3pioou1 o0r1CD7YB13ZqAxuMT+R+2HPAkyFsdI/U61g4UUFl5XYkqOxee0woPpaS76wh4sXxu9K k3o/5IWOQGMcvZf+ZjYvwFfcUYpR913h6R8vrMekgfHmtd2pp6N/2ccDNkEbsEapDQEc +sbDP28/mSQpMhSE6E7kXpuJUnjuM9qXjYCce+A8n/etR0RX12ZTrIzfaHPE/zIg59YF jq+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=t902PH78; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f5si730872edw.358.2020.12.01.14.16.22; Tue, 01 Dec 2020 14:16:45 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=t902PH78; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728487AbgLAIT4 (ORCPT + 99 others); Tue, 1 Dec 2020 03:19:56 -0500 Received: from mail.kernel.org ([198.145.29.99]:47176 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728193AbgLAITz (ORCPT ); Tue, 1 Dec 2020 03:19:55 -0500 Received: from localhost (83-86-74-64.cable.dynamic.v4.ziggo.nl [83.86.74.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7FEFD2085B; Tue, 1 Dec 2020 08:19:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1606810755; bh=0/yOIYQ98fm3d3u1FxrZ+6Y5Jj/gTetcUK3rSD1zAa4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=t902PH78vejIKt9/oIji5wZ3DjzlRhnwu3eYsRbwg/CWslYw7nbCdkcgEdwR4175w uuC5l45f1FM66NEZ7BPb1LVrc7xg5uGM0J8U+pVcbsmX7Jm/hj5WjGBsqw1M2RM3bO ZtzV1br9AYFBwyS9KsO7fZ1Q8EP4XgKphPnZ+Cf4= Date: Tue, 1 Dec 2020 09:20:27 +0100 From: Greg Kroah-Hartman To: Nick Desaulniers Cc: Naresh Kamboju , linux-stable , open list , lkft-triage@lists.linaro.org, Sasha Levin , clang-built-linux , x86@vger.kernel.org, Matthias Kaehlcke Subject: Re: [stable 4.9] PANIC: double fault, error_code: 0x0 - clang boot failed on x86_64 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 30, 2020 at 12:12:39PM -0800, Nick Desaulniers wrote: > 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 for the info. Naresh, does this help explain why maybe testing these kernel branches with clang might not be the best thing to do? greg k-h