linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Dexuan Cui <decui@microsoft.com>, Christoph Hellwig <hch@lst.de>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Michael Kelley <mikelley@microsoft.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	KY Srinivasan <kys@microsoft.com>
Subject: Re: hv_hypercall_pg page permissios
Date: Tue, 16 Jun 2020 11:33:41 +0200	[thread overview]
Message-ID: <20200616093341.GA26400@lst.de> (raw)
In-Reply-To: <87blljicjm.fsf@vitty.brq.redhat.com>

On Tue, Jun 16, 2020 at 11:29:33AM +0200, Vitaly Kuznetsov wrote:
> it seems we need something like PAGE_KERNEL_READONLY_EXEC but we don't
> seem to have one on x86. Hypercall page is special in a way that the
> guest doesn't need to write there at all. vmalloc_exec() seems to have
> only one other user on x86: module_alloc() and it has other needs.

module_alloc actually is a weak function and overriden on x86 (and many
other architectures) , so it isn't used either (did I mention that I hate
weak functions?)

> On
> ARM, alloc_insn_page() does the following:



> 
> arch/arm64/kernel/probes/kprobes.c:     page = vmalloc_exec(PAGE_SIZE);
> arch/arm64/kernel/probes/kprobes.c-     if (page) {
> arch/arm64/kernel/probes/kprobes.c-             set_memory_ro((unsigned long)page, 1);
> arch/arm64/kernel/probes/kprobes.c-             set_vm_flush_reset_perms(page);
> arch/arm64/kernel/probes/kprobes.c-     }
> 
> What if we do the same? (almost untested):
> 
> diff --git a/arch/x86/hyperv/hv_init.c b/arch/x86/hyperv/hv_init.c
> index e2137070386a..31aadfea589b 100644
> --- a/arch/x86/hyperv/hv_init.c
> +++ b/arch/x86/hyperv/hv_init.c
> @@ -23,6 +23,7 @@
>  #include <linux/kernel.h>
>  #include <linux/cpuhotplug.h>
>  #include <linux/syscore_ops.h>
> +#include <linux/set_memory.h>
>  #include <clocksource/hyperv_timer.h>
>  
>  void *hv_hypercall_pg;
> @@ -383,6 +384,8 @@ void __init hyperv_init(void)
>                 wrmsrl(HV_X64_MSR_GUEST_OS_ID, 0);
>                 goto remove_cpuhp_state;
>         }
> +       set_memory_ro((unsigned long)hv_hypercall_pg, 1);
> +       set_vm_flush_reset_perms(hv_hypercall_pg);

This should work and might be the best for 5.8, but I think we need
to sort this whole mess out for real.

  reply	other threads:[~2020-06-16  9:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07  6:55 hv_hypercall_pg page permissios Christoph Hellwig
2020-04-07  7:28 ` Vitaly Kuznetsov
2020-04-07  7:38   ` Christoph Hellwig
2020-04-07 21:01     ` Andy Lutomirski
2020-06-12  7:48       ` Dexuan Cui
2020-06-15  8:35         ` Vitaly Kuznetsov
2020-06-15 17:41           ` Dexuan Cui
2020-06-15 19:49             ` Dexuan Cui
2020-06-16  7:23               ` Christoph Hellwig
2020-06-16 10:18                 ` Peter Zijlstra
2020-06-16 10:23                   ` Christoph Hellwig
2020-06-16 10:24                     ` Christoph Hellwig
2020-06-16 10:31                       ` Peter Zijlstra
2020-06-16 10:33                         ` Christoph Hellwig
2020-06-16 10:40                           ` Peter Zijlstra
2020-06-16 10:42                             ` Christoph Hellwig
2020-06-16 10:52                               ` Christoph Hellwig
2020-06-16 11:24                                 ` Peter Zijlstra
2020-06-16 14:39                                   ` Christoph Hellwig
2020-06-16  9:29               ` Vitaly Kuznetsov
2020-06-16  9:33                 ` Christoph Hellwig [this message]
2020-06-16  9:55                   ` Christoph Hellwig
2020-06-16 10:08                     ` Christoph Hellwig
2020-06-16 10:50                       ` Vitaly Kuznetsov
2020-06-16 10:20                     ` Peter Zijlstra
2020-04-07 18:10   ` Dexuan Cui
2020-04-07 20:42     ` Wei Liu

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=20200616093341.GA26400@lst.de \
    --to=hch@lst.de \
    --cc=decui@microsoft.com \
    --cc=juhlee@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=peterz@infradead.org \
    --cc=stephen@networkplumber.org \
    --cc=vkuznets@redhat.com \
    --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).