All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
	Alexander Graf <agraf@suse.de>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	linux-s390 <linux-s390@vger.kernel.org>,
	"Jason J. Herne" <jjherne@us.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [GIT PULL 2/9] KVM: s390: Cleanup usage of current->mm in set_guest_storage_key
Date: Tue, 28 Oct 2014 20:39:52 +0100	[thread overview]
Message-ID: <1414525199-53989-3-git-send-email-borntraeger@de.ibm.com> (raw)
In-Reply-To: <1414525199-53989-1-git-send-email-borntraeger@de.ibm.com>

From: "Jason J. Herne" <jjherne@us.ibm.com>

In set_guest_storage_key, we really want to reference the mm struct given as
a parameter to the function. So replace the current->mm reference with the
mm struct passed in by the caller.

Signed-off-by: Jason J. Herne <jjherne@us.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
 arch/s390/mm/pgtable.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/s390/mm/pgtable.c b/arch/s390/mm/pgtable.c
index 1b79ca6..cfecc24 100644
--- a/arch/s390/mm/pgtable.c
+++ b/arch/s390/mm/pgtable.c
@@ -936,7 +936,7 @@ int set_guest_storage_key(struct mm_struct *mm, unsigned long addr,
 
 	down_read(&mm->mmap_sem);
 retry:
-	ptep = get_locked_pte(current->mm, addr, &ptl);
+	ptep = get_locked_pte(mm, addr, &ptl);
 	if (unlikely(!ptep)) {
 		up_read(&mm->mmap_sem);
 		return -EFAULT;
-- 
1.9.3

  parent reply	other threads:[~2014-10-28 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 19:39 [GIT PULL 0/9] KVM: s390: Fixes and cleanups for kvm/next (3.19) Christian Borntraeger
2014-10-28 19:39 ` [GIT PULL 1/9] KVM: s390: Make the simple ipte mutex specific to a VM instead of global Christian Borntraeger
2014-10-28 19:39 ` Christian Borntraeger [this message]
2014-10-28 19:39 ` [GIT PULL 3/9] KVM: s390: Fix size of monitor-class number field Christian Borntraeger
2014-10-28 19:39 ` [GIT PULL 4/9] KVM: s390: sigp: dispatch orders with one target in a separate function Christian Borntraeger
2014-10-28 19:39 ` [GIT PULL 5/9] KVM: s390: sigp: move target cpu checks into dispatcher Christian Borntraeger
2014-10-28 19:39 ` [GIT PULL 6/9] KVM: s390: sigp: separate preparation handlers Christian Borntraeger
2014-10-28 19:39 ` [GIT PULL 7/9] KVM: s390: sigp: instruction counters for all sigp orders Christian Borntraeger
2014-10-28 19:39 ` [GIT PULL 8/9] KVM: s390: sigp: inject emergency calls in a separate function Christian Borntraeger
2014-10-28 19:39 ` [GIT PULL 9/9] KVM: s390: sigp: split handling of SIGP STOP (AND STORE STATUS) Christian Borntraeger
2014-10-29 11:56 ` [GIT PULL 0/9] KVM: s390: Fixes and cleanups for kvm/next (3.19) Paolo Bonzini

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=1414525199-53989-3-git-send-email-borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=jjherne@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.