From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 280E8C3A5A5 for ; Thu, 5 Sep 2019 12:08:40 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 5F04821848 for ; Thu, 5 Sep 2019 12:08:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5F04821848 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 46PKGX6p2WzDqy9 for ; Thu, 5 Sep 2019 22:08:36 +1000 (AEST) Received: from ozlabs.org (bilbo.ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 46PKCC3znGzDqfS for ; Thu, 5 Sep 2019 22:05:43 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Received: by ozlabs.org (Postfix, from userid 1034) id 46PKCB17dzz9sPG; Thu, 5 Sep 2019 22:05:41 +1000 (AEST) X-powerpc-patch-notification: thanks X-powerpc-patch-commit: 8205d5d98ef7f155de211f5e2eb6ca03d95a5a60 In-Reply-To: <20190904045529.23002-1-gromero@linux.vnet.ibm.com> To: gromero , linuxppc-dev@lists.ozlabs.org, mikey@neuling.org From: Michael Ellerman Subject: Re: [PATCH v2 1/3] powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction Message-Id: <46PKCB17dzz9sPG@ozlabs.org> Date: Thu, 5 Sep 2019 22:05:41 +1000 (AEST) X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: cyrilbur@gmail.com, gromero@linux.vnet.ibm.com Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Wed, 2019-09-04 at 04:55:27 UTC, gromero wrote: > From: Gustavo Romero > > When we take an FP unavailable exception in a transaction we have to > account for the hardware FP TM checkpointed registers being > incorrect. In this case for this process we know the current and > checkpointed FP registers must be the same (since FP wasn't used > inside the transaction) hence in the thread_struct we copy the current > FP registers to the checkpointed ones. ... > > This fixes CVE-2019-15030. > > Fixes: f48e91e87e67 ("powerpc/tm: Fix FP and VMX register corruption") > Cc: stable@vger.kernel.org # 4.12+ > Signed-off-by: Gustavo Romero > Signed-off-by: Michael Neuling Applied to powerpc fixes, thanks. https://git.kernel.org/powerpc/c/8205d5d98ef7f155de211f5e2eb6ca03d95a5a60 cheers