From: Nathan Chancellor <natechancellor@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Arnd Bergmann <arnd@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Nick Desaulniers <ndesaulniers@google.com>,
Arnd Bergmann <arnd@arndb.de>, Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-efi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com
Subject: Re: [PATCH] x86: efi: avoid BUILD_BUG_ON() for non-constant p4d_index
Date: Fri, 15 Jan 2021 11:32:03 -0700 [thread overview]
Message-ID: <20210115183203.GA1991122@ubuntu-m3-large-x86> (raw)
In-Reply-To: <20210115182300.GD9138@zn.tnic>
On Fri, Jan 15, 2021 at 07:23:00PM +0100, Borislav Petkov wrote:
> On Thu, Jan 07, 2021 at 11:34:15PM +0100, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > When 5-level page tables are enabled, clang triggers a BUILD_BUG_ON():
>
> I have CONFIG_X86_5LEVEL=y, CONFIG_EFI=y and am using Debian clang
> version 10.0.1-8+b1 but my .config builds just fine.
>
> How do you trigger this?
I triggered it with CONFIG_UBSAN=y + CONFIG_UBSAN_UNSIGNED_OVERFLOW=y
(it can be exposed with an allyesconfig/allmodconfig on mainline
currently).
Cheers,
Nathan
next prev parent reply other threads:[~2021-01-15 18:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 22:34 [PATCH] x86: efi: avoid BUILD_BUG_ON() for non-constant p4d_index Arnd Bergmann
2021-01-07 22:42 ` Nathan Chancellor
2021-01-13 17:51 ` Ard Biesheuvel
2021-01-15 18:23 ` Borislav Petkov
2021-01-15 18:32 ` Nathan Chancellor [this message]
2021-01-15 19:07 ` Borislav Petkov
2021-01-15 19:11 ` Arvind Sankar
2021-01-15 19:18 ` Borislav Petkov
2021-01-15 19:54 ` Arnd Bergmann
2021-01-15 20:12 ` Arvind Sankar
2021-01-15 20:32 ` Arvind Sankar
2021-01-15 19:07 ` Arvind Sankar
2021-01-15 20:27 ` Arvind Sankar
2021-01-16 16:34 ` Ard Biesheuvel
2021-01-18 20:24 ` Borislav Petkov
2021-01-18 21:42 ` Arvind Sankar
2021-01-20 9:33 ` Ard Biesheuvel
2021-01-20 11:44 ` Borislav Petkov
2021-02-03 18:51 ` Nathan Chancellor
2021-02-03 20:29 ` Ard Biesheuvel
2021-02-04 10:51 ` Borislav Petkov
2021-02-04 10:59 ` Ard Biesheuvel
2021-02-04 19:16 ` Nathan Chancellor
2021-02-04 21:43 ` Arvind Sankar
2021-02-04 22:13 ` Borislav Petkov
2021-02-05 0:08 ` Arvind Sankar
2021-02-05 11:39 ` [PATCH] x86/efi: Remove EFI PGD build time checks Borislav Petkov
2021-02-05 11:57 ` Ard Biesheuvel
2021-02-05 18:14 ` Nick Desaulniers
2021-02-05 18:56 ` Nathan Chancellor
2021-02-05 10:34 ` [PATCH] x86: efi: avoid BUILD_BUG_ON() for non-constant p4d_index Borislav Petkov
2021-02-05 18:27 ` Nick Desaulniers
2021-02-05 18:31 ` Nathan Chancellor
2021-01-20 11:26 ` Kirill A. Shutemov
2021-01-20 11:06 ` Kirill A. Shutemov
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=20210115183203.GA1991122@ubuntu-m3-large-x86 \
--to=natechancellor@gmail.com \
--cc=andy@infradead.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=clang-built-linux@googlegroups.com \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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).