From mboxrd@z Thu Jan  1 00:00:00 1970
From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH 1/3] kvm: keep track of which task is running a KVM
 vcpu
Date: Fri, 3 Dec 2010 17:47:46 +0530
Message-ID: <20101203121746.GE27994@linux.vnet.ibm.com>
References: <20101202144129.4357fe00@annuminas.surriel.com>
 <20101202144324.4a79263b@annuminas.surriel.com>
Reply-To: vatsa@linux.vnet.ibm.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Avi Kiviti <avi@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@elte.hu>,
	Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Rik van Riel <riel@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20101202144324.4a79263b@annuminas.surriel.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Thu, Dec 02, 2010 at 02:43:24PM -0500, Rik van Riel wrote:
>  	mutex_lock(&vcpu->mutex);
> +	vcpu->task = current;

Shouldn't we grab reference to current task_struct before storing a pointer to 
it?

- vatsa