Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751829AbbESVPI (ORCPT ); Tue, 19 May 2015 17:15:08 -0400 Received: from mailapp01.imgtec.com ([195.59.15.196]:18104 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751209AbbESVPG (ORCPT ); Tue, 19 May 2015 17:15:06 -0400 Subject: [PATCH 2/2] MIPS: MSA: bugfix of keeping MSA live context through clone or fork From: Leonid Yegoshin To: , , , , , , , , , , , , , Date: Tue, 19 May 2015 14:13:59 -0700 Message-ID: <20150519211359.35859.24907.stgit@ubuntu-yegoshin> In-Reply-To: <20150519211222.35859.52798.stgit@ubuntu-yegoshin> References: <20150519211222.35859.52798.stgit@ubuntu-yegoshin> User-Agent: StGit/0.17.1-dirty MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.20.3.79] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1223 Lines: 33 It seems the patch 39148e94e3e1f0477ce8ed3fda00123722681f3a "MIPS: fork: Fix MSA/FPU/DSP context duplication race" assumes that DSP/FPU and MSA context should be inherited in child at clone/fork (look into patch description). It was done on Matthew Fortune request from toolchain team, I guess. Well, in this case it should prevent clearing TIF_MSA_CTX_LIVE in copy_thread(). Signed-off-by: Leonid Yegoshin --- arch/mips/kernel/process.c | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/mips/kernel/process.c b/arch/mips/kernel/process.c index f2975d4d1e44..a16e62d40210 100644 --- a/arch/mips/kernel/process.c +++ b/arch/mips/kernel/process.c @@ -163,7 +163,6 @@ int copy_thread(unsigned long clone_flags, unsigned long usp, clear_tsk_thread_flag(p, TIF_USEDFPU); clear_tsk_thread_flag(p, TIF_USEDMSA); - clear_tsk_thread_flag(p, TIF_MSA_CTX_LIVE); #ifdef CONFIG_MIPS_MT_FPAFF clear_tsk_thread_flag(p, TIF_FPUBOUND); -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/