From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH v6 1/4] x86/xen: Probe target addresses in set_aliased_prot before the hypercall Date: Fri, 31 Jul 2015 10:41:07 +0100 Message-ID: <55BB42B3.1040103__39361.9961142123$1438335759$gmane$org@citrix.com> References: <0b0e55b995cda11e7829f140b833ef932fcabe3a.1438291540.git.luto@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0b0e55b995cda11e7829f140b833ef932fcabe3a.1438291540.git.luto@kernel.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andy Lutomirski , X86 ML , Borislav Petkov , "linux-kernel@vger.kernel.org" Cc: "security@kernel.org" , Peter Zijlstra , Andrew Cooper , stable@vger.kernel.org, xen-devel , Steven Rostedt , Jan Beulich , Sasha Levin , Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org On 30/07/15 22:31, Andy Lutomirski wrote: > The update_va_mapping hypercall can fail if the VA isn't present in > the guest's page tables. Under certain loads, this can result in an > OOPS when the target address is in unpopulated vmap space. > > While we're at it, add comments to help explain what's going on. > > This isn't a great long-term fix. This code should probably be > changed to use something like set_memory_ro. Reviewed-by: David Vrabel Thanks. David