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: <20260119132811.GDaW4xazonIcw9g0DY@fat_crate.local>
Date: Mon, 19 Jan 2026 14:28:11 +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 Mon, Jan 19, 2026 at 12:52:50PM +0100, Jürgen Groß wrote:
> So do you want me to resend the series triggering the issue with this patch
> prepended, or are you fine with applying this patch to the tip branch for
> the next merge window, and wait for the other series to get the needed Acks?

Or, you could redesign your set in a way so that the build error doesn't
happen and there's no need for an urgent patch with a questionable Fixes: tag?

Also, the "pure luck" thing would need debugging too, to figure out why the
build error happens.

-- 
Regards/Gruss,
    Boris.

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