From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932382AbcHIUCb (ORCPT ); Tue, 9 Aug 2016 16:02:31 -0400 Received: from mx2.suse.de ([195.135.220.15]:45029 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752429AbcHIUC3 (ORCPT ); Tue, 9 Aug 2016 16:02:29 -0400 Date: Tue, 9 Aug 2016 22:02:25 +0200 (CEST) From: Jiri Kosina X-X-Sender: jkosina@pobox.suse.cz To: "Rafael J. Wysocki" cc: Thomas Garnier , "Rafael J. Wysocki" , Linux PM list , the arch/x86 maintainers , Linux Kernel Mailing List , Yinghai Lu , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Kees Cook , Pavel Machek , Kernel Hardening , Borislav Petkov Subject: Re: [Resend][PATCH] x86/power/64: Always create temporary identity mapping correctly In-Reply-To: Message-ID: References: <2206547.eDj3RJQyE5@vostro.rjw.lan> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 9 Aug 2016, Rafael J. Wysocki wrote: > I have a murky suspicion, but it is really weird. Namely, what if > restore_jump_address in set_up_temporary_text_mapping() happens to be > covered by the restore kernel's identity mapping? Then, the image > kernel's entry point may get overwritten by something else in > core_restore_code(). So this made me to actually test a scenario where I'd suspend a kernel that's known-broken (i.e. contains 021182e52fe), and then have it resumed by a kernel that has 021182e52fe reverted. It resumed successfully. Just a datapoint. -- Jiri Kosina SUSE Labs