linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	linux-stable <stable@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org, Sasha Levin <sashal@kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	x86@vger.kernel.org, Matthias Kaehlcke <mka@chromium.org>
Subject: Re: [stable 4.9] PANIC: double fault, error_code: 0x0 - clang boot failed on x86_64
Date: Tue, 1 Dec 2020 09:20:27 +0100	[thread overview]
Message-ID: <X8X8y4j9Ip+C5DwS@kroah.com> (raw)
In-Reply-To: <CAKwvOdmfEY6fnNFUUzLvN9bKyeTt7OMc-Uvx=YqTuMR2BuD5XA@mail.gmail.com>

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
> <gregkh@linuxfoundation.org> 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

  reply	other threads:[~2020-12-01  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26  4:44 [stable 4.9] PANIC: double fault, error_code: 0x0 - clang boot failed on x86_64 Naresh Kamboju
2020-11-26  6:39 ` Greg Kroah-Hartman
2020-11-28  5:41   ` Nathan Chancellor
2020-11-30 20:12   ` Nick Desaulniers
2020-12-01  8:20     ` Greg Kroah-Hartman [this message]
2020-12-01  9:01       ` Naresh Kamboju
2020-12-01 20:10       ` Nick Desaulniers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=X8X8y4j9Ip+C5DwS@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mka@chromium.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=ndesaulniers@google.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).