public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Carsten Otte <carsteno@de.ibm.com>
Cc: Alexander Graf <agraf@suse.de>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	KVM list <kvm@vger.kernel.org>,
	stable@kernel.org, Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: Fix prefix register checking in arch/s390/kvm/sigp.c
Date: Wed, 02 Dec 2009 14:55:48 +0200	[thread overview]
Message-ID: <4B1663D4.5050003@redhat.com> (raw)
In-Reply-To: <4B13EF71.3080905@de.ibm.com>

On 11/30/2009 06:14 PM, Carsten Otte wrote:
> This patch corrects the checking of the new address for the prefix register.
> On s390, the prefix register is used to address the cpu's lowcore (address
> 0...8k). This check is supposed to verify that the memory is readable and
> present.
> copy_from_guest is a helper function, that can be used to read from guest
> memory. It applies prefixing, adds the start address of the guest memory in
> user, and then calls copy_from_user. Previous code was obviously broken for
> two reasons:
> - prefixing should not be applied here. The current prefix register is
>    going to be updated soon, and the address we're looking for will be
>    0..8k after we've updated the register
> - we're adding the guest origin (gmsor) twice: once in subject code
>    and once in copy_from_guest
>
> With kuli, we did not hit this problem because (a) we were lucky with
> previous prefix register content, and (b) our guest memory was mmaped
> very low into user address space.
>
>    

Applied, thanks.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-12-02 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 16:14 Fix prefix register checking in arch/s390/kvm/sigp.c Carsten Otte
2009-12-02 12:55 ` Avi Kivity [this message]

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=4B1663D4.5050003@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=carsteno@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=stable@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