All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	open list <linux-kernel@vger.kernel.org>,
	clang-built-linux <llvm@lists.linux.dev>,
	Linux Regressions <regressions@lists.linux.dev>,
	lkft-triage@lists.linaro.org,
	Nathan Chancellor <nathan@kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>,
	dwmw@amazon.co.uk, "H. Peter Anvin" <hpa@zytor.com>,
	Kees Cook <keescook@chromium.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: next-20250407: qemu_x86_64 clang-20, clang-nightly no console log but gcc-13 boot pass
Date: Mon, 7 Apr 2025 19:47:36 +0200	[thread overview]
Message-ID: <Z_QPuPmtrFOnhjeP@gmail.com> (raw)
In-Reply-To: <CAMj1kXH+z4zAhxMucg5NeaOpfp2p69=sqL78JiwvEsWNjFaJOQ@mail.gmail.com>


* Ard Biesheuvel <ardb@kernel.org> wrote:

> On Mon, 7 Apr 2025 at 18:17, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > On Mon, 7 Apr 2025 at 17:15, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > >
> > > Regressions on qemu-x86_64 with clang-20 and clang-nightly on the
> > > Linux next-20250407 and no console output.
> > >
> > > The gcc-13 builds boot pass on qemu-x86_64.
> > >
> > > First seen on the next-20250407.
> > > Bad: next-20250407
> > > Good:next-20250404
> > >
> > > * qemu-x86_64, boot
> > >  - boot/clang-20-lkftconfig
> > >  - boot/clang-20-lkftconfig-compat
> > >  - boot/clang-nightly-lkftconfig
> > >
> > > Regression Analysis:
> > > - New regression? Yes
> > > - Reproducibility? Yes
> > >
> > > Boot regression: qemu_x86_64 clang-20, clang-nightly no console log
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > Anders bisected this and found,
> > # first bad commit:
> >    [cc34e658c6db493c1524077e95b42d478de58f2b]
> >    x86/boot: Move the early GDT/IDT setup code into startup/
> >
> > Lore report link,
> >  - https://lore.kernel.org/all/CA+G9fYt4VVa3kUDR+ze05xM+fRmMBVfbBTsypUq5oOpAfuzjfg@mail.gmail.com/
> >
> 
> Thanks for the report. I'll look into this.

I've zapped cc34e658c6db from tip:x86/boot for the time being.

I have the same request as for the other patches applies, please split 
it up into ~3 patches for better bisectability and ease of review:

 - first the mechanic movement of code, with very few changes (if the 
   result builds & boots),

 - then drop the RIP_REL_REF() uses in the second patch,

 - and drop __head annotations in the third patch.

Thanks,

	Ingo

      reply	other threads:[~2025-04-07 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 11:45 next-20250407: qemu_x86_64 clang-20, clang-nightly no console log but gcc-13 boot pass Naresh Kamboju
2025-04-07 15:17 ` Naresh Kamboju
2025-04-07 15:56   ` Ard Biesheuvel
2025-04-07 17:47     ` Ingo Molnar [this message]

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=Z_QPuPmtrFOnhjeP@gmail.com \
    --to=mingo@kernel.org \
    --cc=anders.roxell@linaro.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=dwmw@amazon.co.uk \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=llvm@lists.linux.dev \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.