linux-kernel - Re: [PATCH] arch/x86/entry_fred: don't set up KVM IRQs if KVM is disabled

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: <CAKPOu+9oqRHJTpxd4+yoNYLPP6fNihuivCfNKfOD=f-X2WD04g@mail.gmail.com>
Date: Thu, 15 Feb 2024 20:30:19 +0100
From: Max Kellermann <max.kellermann@...os.com>
To: Xin Li <xin@...or.com>
Cc: hpa@...or.com, x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arch/x86/entry_fred: don't set up KVM IRQs if KVM is disabled

On Thu, Feb 15, 2024 at 7:23 PM Xin Li <xin@...or.com> wrote:
> The POSTED_INTR_* macros are under CONFIG_HAVE_KVM, which is 'selected'
> under CONFIG_X86.

Sorry, I should have said that I found this bug on linux-next master,
which has this commit:

https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next/+/dcf0926e9b899eca754a07c4064de69815b85a38%5E%21/

. which changes CONFIG_HAVE_KVM to CONFIG_KVM. I was not aware that
this commit hadn't been merged upstream yet.

You can easily reproduce with with "defconfig" plus CONFIG_X86_FRED
(on linux-next/master).

Max