linux-kernel - Re: [KVM PATCH] KVM: introduce "xinterface" API for external interaction with guests

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]

Date:	Thu, 16 Jul 2009 11:09:50 -0500
From:	Anthony Liguori <aliguori@...ibm.com>
To:	Gregory Haskins <ghaskins@...ell.com>
CC:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org, avi@...hat.com,
	glommer@...hat.com
Subject: Re: [KVM PATCH] KVM: introduce "xinterface" API for external interaction
 with guests

Gregory Haskins wrote:
> That said, I think the assumption that was made when I was using this
> was that a proper ref for the page was acquired by the gfn_to_page() and
> dropped by the caller.  This was always used in the context of a
> hypercall/vmexit so presumably the gpa should be considered stable
> across that call.  Is that not true?
>   

If you're in kvm.ko, then yes, that's a safe assumption to make because 
the guest VCPU cannot run while you are running.

But you're opening this interface to any caller so the VCPU is likely to 
be running while someone calls this function

> Regards,
> -Greg
>
>
>   


-- 
Regards,

Anthony Liguori

--
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/