lkml.org 
[lkml]   [2020]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [stable 4.9] PANIC: double fault, error_code: 0x0 - clang boot failed on x86_64
On Tue, 1 Dec 2020 at 13:49, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Mon, Nov 30, 2020 at 12:12:39PM -0800, Nick Desaulniers wrote:
> >
> > (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?

It is clear now.

FYI,
With this note LKFT will not test 4.14+clang and old branches.

- Naresh

\
 
 \ /
  Last update: 2020-12-01 10:10    [W:0.080 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site