linux-kernel - Re: [PATCH 5/5] KVM: x86: allow defining return-0 static calls

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: <Yf/WvmqxzBDVTTSm@hirez.programming.kicks-ass.net>
Date:   Sun, 6 Feb 2022 15:10:06 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
        seanjc@...gle.com
Subject: Re: [PATCH 5/5] KVM: x86: allow defining return-0 static calls

On Thu, Feb 03, 2022 at 07:40:25PM +0100, Paolo Bonzini wrote:
> On 2/2/22 19:18, Paolo Bonzini wrote:
> > A few vendor callbacks are only used by VMX, but they return an integer
> > or bool value.  Introduce KVM_X86_OP_RET0 for them: a NULL value in
> > struct kvm_x86_ops will be changed to __static_call_return0.
> 
> This also needs EXPORT_SYMBOL_GPL(__static_call_ret0).  Peter, any
> objections?

__static_call_return0 I suppose, but no. Go ahead.