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: <9457a569-c829-74c9-9836-e9bc76a3ca46@redhat.com>
Date:   Thu, 29 Aug 2019 15:34:54 +0200
From:   Thomas Huth <thuth@...hat.com>
To:     Christian Borntraeger <borntraeger@...ibm.com>,
        kvm@...r.kernel.org, Janosch Frank <frankja@...ux.ibm.com>
Cc:     linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
        David Hildenbrand <david@...hat.com>,
        Cornelia Huck <cohuck@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>
Subject: Re: [PATCH v3] KVM: selftests: Add a test for the KVM_S390_MEM_OP
 ioctl

On 29/08/2019 15.26, Christian Borntraeger wrote:
> 
> 
> On 29.08.19 15:07, Thomas Huth wrote:
>> Check that we can write and read the guest memory with this s390x
>> ioctl, and that some error cases are handled correctly.
>>
>> Signed-off-by: Thomas Huth <thuth@...hat.com>
>> ---
>>  v3:
>>  - Replaced wrong copy-n-pasted report string with a proper one
>>  - Check for errno after calling the ioctl with size = 0
> 
> the test succeeds (as the vmalloc fails) but dmesg then has the warning.
> Do we have a chance to parse dmesg somehow?

I'm not aware of an easy way to do this from within the KVM selftests.

> I will apply this nevertheless for the time being together with the fix.

Thanks!

 Thomas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ