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: <048b3f3a-379d-cff3-20b6-fc74dd12a98f@openvz.org>
Date:   Tue, 4 May 2021 11:15:35 +0300
From:   "Denis V. Lunev" <den@...nvz.org>
To:     Paolo Bonzini <pbonzini@...hat.com>,
        Sean Christopherson <seanjc@...gle.com>,
        Valeriy Vdovin <valeriy.vdovin@...tuozzo.com>
Cc:     linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
        Vitaly Kuznetsov <vkuznets@...hat.com>,
        Wanpeng Li <wanpengli@...cent.com>,
        Jim Mattson <jmattson@...gle.com>,
        Joerg Roedel <joro@...tes.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
        Shuah Khan <shuah@...nel.org>,
        Aaron Lewis <aaronlewis@...gle.com>,
        Alexander Graf <graf@...zon.com>,
        Andrew Jones <drjones@...hat.com>,
        Oliver Upton <oupton@...gle.com>,
        Like Xu <like.xu@...ux.intel.com>, kvm@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v4] KVM: x86: Fix KVM_GET_CPUID2 ioctl to return cpuid
 entries count

On 5/4/21 10:23 AM, Paolo Bonzini wrote:
> On 03/05/21 21:18, Denis V. Lunev wrote:
>> On 5/3/21 5:54 PM, Paolo Bonzini wrote:
>>> On 29/04/21 03:00, Sean Christopherson wrote:
>>>> On Wed, Apr 28, 2021, Valeriy Vdovin wrote:
>>>>> It's very explicit by the code that it was designed to receive some
>>>>> small number of entries to return E2BIG along with the corrected
>>>>> number.
>>>>
>>>> LOL, saying KVM_GET_CPUID2 was "designed" is definitely giving the KVM
>>>> forefathers the benefit of the doubt.
>>>
>>> I was going to make a different joke, i.e. that KVM_GET_CPUID2 was
>>> indeed designed the way Valeriy described, but that design was
>>> forgotten soon after.
>>>
>>> Really, this ioctl has been such a trainwreck that I think the only
>>> good solution here is to drop it.
>>>
>>> Paolo
>>>
>>
>> should we discuss KVM_GET_CPUID3 which will work "normally"?
>
> Is anybody using KVM_GET_CPUID2 at all?
>
> Paolo
>
As far as I understand only some testing within kernel now.
Though we have plans to expose it for QAPI as the series
in QEMU
  [PATCH 1/2] qapi: fix error handling for x-vz-query-cpu-model-cpuid
  [PATCH 2/2] qapi: blacklisted x-vz-query-cpu-model-cpuid in tests
is not coming in a good way.
The idea was to avoid manual code rework in QEMU and
expose collected model at least for debug.

All it all, some control over things set to the kernel as CPU modes
is needed. Without that I am feeling uncomfortable.

Den

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ