From: Paul Durrant <xadimgnik@gmail.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
David Woodhouse <dwmw2@infradead.org>,
Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v12 11/20] KVM: xen: allow shared_info to be mapped by fixed HVA
Date: Thu, 8 Feb 2024 16:51:18 +0000 [thread overview]
Message-ID: <148d903c-fcc5-4a6a-aef1-c1e77e74d0fc@xen.org> (raw)
In-Reply-To: <ZcUF-TNbykWvh3r7@google.com>
On 08/02/2024 16:48, Sean Christopherson wrote:
> On Thu, Feb 08, 2024, Paul Durrant wrote:
>> On 07/02/2024 04:10, Sean Christopherson wrote:
>>> On Mon, Jan 15, 2024, Paul Durrant wrote:
>>>> @@ -638,20 +637,32 @@ int kvm_xen_hvm_set_attr(struct kvm *kvm, struct kvm_xen_hvm_attr *data)
>>>> }
>>>> break;
>>>> - case KVM_XEN_ATTR_TYPE_SHARED_INFO: {
>>>> + case KVM_XEN_ATTR_TYPE_SHARED_INFO:
>>>> + case KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA: {
>>>> int idx;
>>>> mutex_lock(&kvm->arch.xen.xen_lock);
>>>> idx = srcu_read_lock(&kvm->srcu);
>>>> - if (data->u.shared_info.gfn == KVM_XEN_INVALID_GFN) {
>>>> - kvm_gpc_deactivate(&kvm->arch.xen.shinfo_cache);
>>>> - r = 0;
>>>> + if (data->type == KVM_XEN_ATTR_TYPE_SHARED_INFO) {
>>>> + if (data->u.shared_info.gfn == KVM_XEN_INVALID_GFN) {
>>>> + kvm_gpc_deactivate(&kvm->arch.xen.shinfo_cache);
>>>> + r = 0;
>>>> + } else {
>>>> + r = kvm_gpc_activate(&kvm->arch.xen.shinfo_cache,
>>>> + gfn_to_gpa(data->u.shared_info.gfn),
>>>> + PAGE_SIZE);
>>>> + }
>>>> } else {
>>>> - r = kvm_gpc_activate(&kvm->arch.xen.shinfo_cache,
>>>> - gfn_to_gpa(data->u.shared_info.gfn),
>>>> - PAGE_SIZE);
>>>> + if (data->u.shared_info.hva == 0) {
>>>
>>> I know I said I don't care about the KVM Xen ABI, but I still think using '0' as
>>> "invalid" is ridiculous.
>>>
>>
>> With the benefit of some sleep, I'm wondering why 0 is a 'ridiculous'
>> invalid value for a *virtual* address? Surely it's essentially a numerical
>> cast of the canonically invalid NULL pointer?
>
> It's legal to mmap() virtual address '0', albeit not by default:
>
> config DEFAULT_MMAP_MIN_ADDR
> int "Low address space to protect from user allocation"
> depends on MMU
> default 4096
> help
> This is the portion of low virtual memory which should be protected
> from userspace allocation. Keeping a user from writing to low pages
> can help reduce the impact of kernel NULL pointer bugs.
>
> For most ppc64 and x86 users with lots of address space
> a value of 65536 is reasonable and should cause no problems.
> On arm and other archs it should not be higher than 32768.
> Programs which use vm86 functionality or have some need to map
> this low address space will need CAP_SYS_RAWIO or disable this
> protection by setting the value to 0.
>
> This value can be changed after boot using the
> /proc/sys/vm/mmap_min_addr tunable.
>
>
> Obviously it's equally ridiculous that userspace would ever mmap() '0' and pass
> that as the shared_info, but given that this is x86-only, there are architecturally
> illegal addresses that can be used, at least until Intel adds LA64 ;-)
Ok. Thanks for the reference.
next prev parent reply other threads:[~2024-02-08 16:51 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 12:56 [PATCH v12 00/20] KVM: xen: update shared_info and vcpu_info handling Paul Durrant
2024-01-15 12:56 ` [PATCH v12 01/20] KVM: pfncache: Add a map helper function Paul Durrant
2024-01-15 12:56 ` [PATCH v12 02/20] KVM: pfncache: remove unnecessary exports Paul Durrant
2024-01-15 12:56 ` [PATCH v12 03/20] KVM: xen: mark guest pages dirty with the pfncache lock held Paul Durrant
2024-02-07 3:17 ` Sean Christopherson
2024-02-07 3:26 ` David Woodhouse
2024-02-07 15:15 ` Sean Christopherson
2024-02-07 8:48 ` Paul Durrant
2024-01-15 12:56 ` [PATCH v12 04/20] KVM: pfncache: add a mark-dirty helper Paul Durrant
2024-02-07 3:20 ` Sean Christopherson
2024-02-07 8:47 ` Paul Durrant
2024-02-09 15:58 ` Sean Christopherson
2024-02-09 16:05 ` Paul Durrant
2024-01-15 12:56 ` [PATCH v12 05/20] KVM: pfncache: remove KVM_GUEST_USES_PFN usage Paul Durrant
2024-01-15 12:56 ` [PATCH v12 06/20] KVM: pfncache: stop open-coding offset_in_page() Paul Durrant
2024-01-15 12:56 ` [PATCH v12 07/20] KVM: pfncache: include page offset in uhva and use it consistently Paul Durrant
2024-01-15 12:56 ` [PATCH v12 08/20] KVM: pfncache: allow a cache to be activated with a fixed (userspace) HVA Paul Durrant
2024-02-07 4:03 ` Sean Christopherson
2024-02-07 4:13 ` David Woodhouse
2024-02-14 16:01 ` Sean Christopherson
2024-02-14 16:09 ` Paul Durrant
2024-02-14 15:21 ` Paul Durrant
2024-02-14 16:20 ` Sean Christopherson
2024-02-14 16:33 ` Paul Durrant
2024-01-15 12:56 ` [PATCH v12 09/20] KVM: xen: separate initialization of shared_info cache and content Paul Durrant
2024-01-15 12:56 ` [PATCH v12 10/20] KVM: xen: re-initialize shared_info if guest (32/64-bit) mode is set Paul Durrant
2024-01-15 12:56 ` [PATCH v12 11/20] KVM: xen: allow shared_info to be mapped by fixed HVA Paul Durrant
2024-02-07 4:10 ` Sean Christopherson
2024-02-07 8:53 ` Paul Durrant
2024-02-08 8:52 ` Paul Durrant
2024-02-08 16:48 ` Sean Christopherson
2024-02-08 16:51 ` Paul Durrant [this message]
2024-02-08 17:26 ` David Woodhouse
2024-02-09 16:01 ` Sean Christopherson
2024-01-15 12:56 ` [PATCH v12 12/20] KVM: xen: allow vcpu_info " Paul Durrant
2024-01-15 12:57 ` [PATCH v12 13/20] KVM: selftests / xen: map shared_info using HVA rather than GFN Paul Durrant
2024-02-07 4:14 ` Sean Christopherson
2024-02-07 8:54 ` Paul Durrant
2024-02-07 14:58 ` Sean Christopherson
2024-01-15 12:57 ` [PATCH v12 14/20] KVM: selftests / xen: re-map vcpu_info using HVA rather than GPA Paul Durrant
2024-01-15 12:57 ` [PATCH v12 15/20] KVM: xen: advertize the KVM_XEN_HVM_CONFIG_SHARED_INFO_HVA capability Paul Durrant
2024-01-15 12:57 ` [PATCH v12 16/20] KVM: xen: split up kvm_xen_set_evtchn_fast() Paul Durrant
2024-01-15 12:57 ` [PATCH v12 17/20] KVM: xen: don't block on pfncache locks in kvm_xen_set_evtchn_fast() Paul Durrant
2024-02-07 4:17 ` Sean Christopherson
2024-02-07 4:21 ` David Woodhouse
2024-01-15 12:57 ` [PATCH v12 18/20] KVM: pfncache: check the need for invalidation under read lock first Paul Durrant
2024-02-07 4:22 ` Sean Christopherson
2024-02-07 4:27 ` David Woodhouse
2024-02-07 4:47 ` Sean Christopherson
2024-02-07 4:59 ` David Woodhouse
2024-02-07 15:10 ` Sean Christopherson
2024-01-15 12:57 ` [PATCH v12 19/20] KVM: xen: allow vcpu_info content to be 'safely' copied Paul Durrant
2024-01-15 12:57 ` [PATCH v12 20/20] KVM: pfncache: rework __kvm_gpc_refresh() to fix locking issues Paul Durrant
2024-01-25 15:03 ` [PATCH v12 00/20] KVM: xen: update shared_info and vcpu_info handling Paul Durrant
2024-01-25 20:07 ` David Woodhouse
2024-01-26 1:19 ` Sean Christopherson
2024-02-02 17:37 ` Paul Durrant
2024-02-02 22:03 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=148d903c-fcc5-4a6a-aef1-c1e77e74d0fc@xen.org \
--to=xadimgnik@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).