linux-kernel - Re: [PATCH] x86/irqflags: Fix build failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260119113653.GBaW4XVYXXgvJtG-Oy@fat_crate.local>
Date: Mon, 19 Jan 2026 12:36:53 +0100
From: Borislav Petkov <bp@...en8.de>
To: Jürgen Groß <jgross@...e.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
	Thomas Gleixner <tglx@...nel.org>, Ingo Molnar <mingo@...hat.com>,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	"H. Peter Anvin" <hpa@...or.com>, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] x86/irqflags: Fix build failure

On Thu, Jan 15, 2026 at 07:29:37PM +0100, Jürgen Groß wrote:
> Yes. The problem was introduced by that patch. It was pure luck paravirt.h
> got included via another header.

So there's no configuration right now which triggers this problem?

> Yes, this would be a possibility. I still can do that, but I saw no real reason
> to resend the other 5 patches without any change.

You mean, you expect me to read minds? :)

> TBH I'm quite puzzled that this build failure hasn't been seen before. As I said
> above: pure luck.

Sorry, we don't do "pure luck."

This either fixes something in the *current* kernel or if not, it should be
applied as an urgent fix when it does after "pure luck" has been debugged
properly and explained.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette