linux-kernel - Re: [PATCH 0/2] kvm/mips: ABI fix for 3.10

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] [day] [month] [year] [list]

Message-ID: <51BF2A8C.5020903@redhat.com>
Date:	Mon, 17 Jun 2013 17:26:04 +0200
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	David Daney <ddaney.cavm@...il.com>
CC:	linux-mips@...ux-mips.org, ralf@...ux-mips.org,
	kvm@...r.kernel.org, Sanjay Lal <sanjayl@...asys.com>,
	Gleb Natapov <gleb@...hat.com>, linux-kernel@...r.kernel.org,
	David Daney <david.daney@...ium.com>
Subject: Re: [PATCH 0/2] kvm/mips: ABI fix for 3.10

Il 10/06/2013 21:33, David Daney ha scritto:
> From: David Daney <david.daney@...ium.com>
> 
> As requested by Gleb Natapov, we need to define and use KVM_REG_MIPS
> when using the GET_ONE_REG/SET_ONE_REG ioctl.  Since this is part of
> the MIPS kvm support that is new in 3.10, it should be merged before a
> bad ABI leaks out into an 'official' kernel release.
> 
> David Daney (2):
>   kvm: Add definition of KVM_REG_MIPS
>   mips/kvm: Use KVM_REG_MIPS and proper size indicators for *_ONE_REG
> 
>  arch/mips/include/uapi/asm/kvm.h | 81 +++++++++++++++++++--------------------
>  arch/mips/kvm/kvm_mips.c         | 83 ++++++++++++++++++++++++++--------------
>  include/uapi/linux/kvm.h         |  1 +
>  3 files changed, 94 insertions(+), 71 deletions(-)
> 

CCed people probably already know, but anyway: this is already in
Linus's tree (commit af180b81a3f4ea925fae88878f367e676e99bf73).

Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/