linux-kernel - Re: [PATCH] KVM: X86: correct meaningless kvm_apicv

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]

Date:   Mon, 16 Mar 2020 08:26:50 -0700
From:   Sean Christopherson <sean.j.christopherson@...el.com>
To:     Vitaly Kuznetsov <vkuznets@...hat.com>
Cc:     Paolo Bonzini <pbonzini@...hat.com>, linmiaohe@...wei.com,
        linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH] KVM: X86: correct meaningless kvm_apicv_activated() check

On Mon, Mar 16, 2020 at 09:33:50AM +0100, Vitaly Kuznetsov wrote:
> Paolo Bonzini <pbonzini@...hat.com> writes:
> > +	if ((old == 0) == (new == 0))
> > +		return;
> 
> This is a very laconic expression I personally find hard to read :-)
> 
> 	/* Check if WE actually changed APICv state */
>         if ((!old && !new) || (old && new))
> 		return;
> 
> would be my preference (not strong though, I read yours several times
> and now I feel like I understand it just fine :-)

Or maybe this to avoid so many equals signs?

	if (!old == !new)
		return;