linux-kernel - Re: KVM selftests are failing

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: <b8246d8c-a50d-2b7b-bea8-b01e945c8f30@redhat.com>
Date:   Fri, 16 Nov 2018 13:08:12 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Ahmed Soliman <ahmedsoliman@...a.vt.edu>,
        Vitaly Kuznetsov <vkuznets@...hat.com>
Cc:     Anders Roxell <anders.roxell@...aro.org>,
        Shuah Khan <shuah@...nel.org>, linux-kselftest@...r.kernel.org,
        Peter Xu <peterx@...hat.com>, linux-kernel@...r.kernel.org,
        Andrew Jones <drjones@...hat.com>
Subject: Re: KVM selftests are failing

On 16/11/18 13:00, Ahmed Soliman wrote:
> Hello once again,
> 
> I noticed that there is still more problems with kvmself test (at
> least on my machine)
> 
> Any test that would successfully reach the guest's code immediately
> VMexit by a shutdown.
> 
> $ ./vmx_tsc_adjust_test
> ==== Test Assertion Failure ====
>  x86_64/vmx_tsc_adjust_test.c:156: run->exit_reason == KVM_EXIT_IO
>  pid=8499 tid=8499 - Success
>     1  0x00005604f07bd36c: ?? ??:0
>     2  0x00007f5c0dc53ae6: ?? ??:0
>     3  0x00005604f07bd4b9: ?? ??:0
>  Got exit_reason other than KVM_EXIT_IO: 8 (SHUTDOWN)
> 
> Also I have got a question I noticed 2 kvm test suites, kvm selftests
> in tools/testing/selftests/kvm/
> and this kvm unit test at [1] I am curious if I should put my tests in
> the kvm unit test intead of kvm selftest

If you are testing the API, or some corner cases and race conditions
that are hard to synthesize with a "real-world" guest, put it here.  If
you are testing the emulated hardware, you probably want to put it in
kvm-unit-tests instead.

Paolo