linux-kernel - Re: [GIT PULL] First batch of KVM changes for 5.6 merge window

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 31 Jan 2020 11:03:17 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Sean Christopherson <sean.j.christopherson@...el.com>
Cc:     Paolo Bonzini <pbonzini@...hat.com>, Borislav Petkov <bp@...e.de>,
        Xiaoyao Li <xiaoyao.li@...el.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] First batch of KVM changes for 5.6 merge window

On Fri, Jan 31, 2020 at 10:53 AM Sean Christopherson
<sean.j.christopherson@...el.com> wrote:
>
> I assume the easiest thing would be send a cleanup patch for vmxfeatures.h
> and route it through the KVM tree?

Probably. The KVM side is the only thing that seems to use the
defines, so any names changes should impact only them (we do have that
mkcapflags.sh script, but that should react automatically to any
changes in the #define names)

And this is obviously not a big deal, I just noticed the discrepancies
when doing that resolution.

                    Linus