From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:49366 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751251AbdHCTWr (ORCPT
        <rfc822;stable@vger.kernel.org>); Thu, 3 Aug 2017 15:22:47 -0400
Date: Thu, 3 Aug 2017 12:22:45 -0700
From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 3/3 v4.9.y] KVM: PPC: Book3S HV: Enable TM before
 accessing TM registers
Message-ID: <20170803192245.GE26218@kroah.com>
References: <20170731010641.ouhqnqbvnnkmp6g4@oak.ozlabs.ibm.com>
 <20170731010830.bq74c24g4nrxl4z6@oak.ozlabs.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170731010830.bq74c24g4nrxl4z6@oak.ozlabs.ibm.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Mon, Jul 31, 2017 at 11:08:30AM +1000, Paul Mackerras wrote:
> commit e47057151422a67ce08747176fa21cb3b526a2c9 upstream.
> 
> Commit 46a704f8409f ("KVM: PPC: Book3S HV: Preserve userspace HTM state
> properly", 2017-06-15) added code to read transactional memory (TM)
> registers but forgot to enable TM before doing so.  The result is
> that if userspace does have live values in the TM registers, a KVM_RUN
> ioctl will cause a host kernel crash like this:
> 

I also have already taken this one, right?