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=-3.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, USER_AGENT_MUTT 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 5BE50C0044C for ; Sat, 3 Nov 2018 12:51:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0972E20833 for ; Sat, 3 Nov 2018 12:51:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="ArRcNdv8" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0972E20833 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728498AbeKCWCl (ORCPT ); Sat, 3 Nov 2018 18:02:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:41890 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728025AbeKCWCk (ORCPT ); Sat, 3 Nov 2018 18:02:40 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E0B932082D; Sat, 3 Nov 2018 12:51:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541249486; bh=cc2lXCQF57obQ2mnOhivVVJ4RVMBEf91shoxocxZTvk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ArRcNdv8NZDDRZvnnvED36QUoj2VX7sIwgBJ2S3Trh9lNlhFA7zK0+FkU1milieU7 xtFYS4uUL0+YVWvcMYaBV/lZP1OAEErfybnf7wP6Vtn++m9bsXOHpLfnhDGTHhxSdG RdvyOPI3bTlGD5OTB0uB/cvmTdthe1M84yrhzCeA= Date: Sat, 3 Nov 2018 08:51:24 -0400 From: Sasha Levin To: Greg Kroah-Hartman Cc: Sudip Mukherjee , linux-kernel , Stable , Jarkko Nikula , Andy Lutomirski , Thomas Gleixner , a.p.zijlstra@chello.nl, Borislav Petkov , Linus Torvalds , Ingo Molnar Subject: Re: [PATCH 4.14 053/143] x86/power: Fix some ordering bugs in __restore_processor_context() Message-ID: <20181103125124.GN194472@sasha-vm> References: <20181102182857.064326086@linuxfoundation.org> <20181102182901.303280657@linuxfoundation.org> <20181102231734.GI194472@sasha-vm> <20181103084016.GA9057@kroah.com> <20181103084151.GB9057@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20181103084151.GB9057@kroah.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Nov 03, 2018 at 09:41:51AM +0100, Greg Kroah-Hartman wrote: >On Sat, Nov 03, 2018 at 09:40:16AM +0100, Greg Kroah-Hartman wrote: >> On Fri, Nov 02, 2018 at 07:17:34PM -0400, Sasha Levin wrote: >> > On Fri, Nov 02, 2018 at 08:19:36PM +0000, Sudip Mukherjee wrote: >> > > Hi Greg, >> > > >> > > On Fri, Nov 2, 2018 at 6:51 PM Greg Kroah-Hartman >> > > wrote: >> > > > >> > > > 4.14-stable review patch. If anyone has any objections, please let me know. >> > > >> > > This has been fixed by another upstream commit: >> > > 7ee18d677989 ("x86/power: Make restore_processor_context() sane") >> > > >> > > You can not directly apply it, will need backporting. >> > >> > It depends on the following commits: >> > >> > 5b06bbcfc2c6 x86/power: Fix some ordering bugs in __restore_processor_context() >> > 090edbe23ff5 x86/power/64: Use struct desc_ptr for the IDT in struct saved_context >> > 896c80bef4d3 x86/power/32: Move SYSENTER MSR restoration to fix_processor_context() >> > 7ee18d677989 x86/power: Make restore_processor_context() sane >> > >> > Greg, any objections to pulling them all in? >> >> No objection, but can I just drop this patch here (it's also in the 4.9 >> queue) and then all of these be added to your next round of patches to >> be pulled in after this release? >> >> That should make it easier, and more ovbious to test this all together. > >I've now dropped this patch from the 4.9 and 4.14 queues as that makes >sense here. Thanks Greg, I'll prepare all 5 for the next cycle. -- Thanks, Sasha