From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751674AbbBPTmu (ORCPT ); Mon, 16 Feb 2015 14:42:50 -0500 Received: from mail.skyhub.de ([78.46.96.112]:52851 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751630AbbBPTms (ORCPT ); Mon, 16 Feb 2015 14:42:48 -0500 Date: Mon, 16 Feb 2015 20:42:01 +0100 From: Borislav Petkov To: Kees Cook Cc: Jiri Kosina , "H. Peter Anvin" , LKML , live-patching@vger.kernel.org, Linux-MM , "x86@kernel.org" Subject: Re: [PATCH v2] x86, kaslr: propagate base load address calculation Message-ID: <20150216194201.GK4458@pd.tnic> References: <20150216115517.GB9500@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 16, 2015 at 11:27:42AM -0800, Kees Cook wrote: > > Well, we can apply the rule of the last setting sticks and since the > > kernel is always going to be adding the last setup_data element of > > type SETUP_KASLR (the boot loader ones will be somewhere on the list > > in-between and we add to the end), we're fine, no? > > Sounds good to me! Ok, thanks. I'll pick it up and route it through the proper channels. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by kanga.kvack.org (Postfix) with ESMTP id E5E696B0032 for ; Mon, 16 Feb 2015 14:42:49 -0500 (EST) Received: by mail-wi0-f181.google.com with SMTP id r20so28475487wiv.2 for ; Mon, 16 Feb 2015 11:42:49 -0800 (PST) Received: from mail.skyhub.de (mail.skyhub.de. [2a01:4f8:120:8448::d00d]) by mx.google.com with ESMTP id da6si24538489wjb.92.2015.02.16.11.42.47 for ; Mon, 16 Feb 2015 11:42:48 -0800 (PST) Date: Mon, 16 Feb 2015 20:42:01 +0100 From: Borislav Petkov Subject: Re: [PATCH v2] x86, kaslr: propagate base load address calculation Message-ID: <20150216194201.GK4458@pd.tnic> References: <20150216115517.GB9500@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Kees Cook Cc: Jiri Kosina , "H. Peter Anvin" , LKML , live-patching@vger.kernel.org, Linux-MM , "x86@kernel.org" On Mon, Feb 16, 2015 at 11:27:42AM -0800, Kees Cook wrote: > > Well, we can apply the rule of the last setting sticks and since the > > kernel is always going to be adding the last setup_data element of > > type SETUP_KASLR (the boot loader ones will be somewhere on the list > > in-between and we add to the end), we're fine, no? > > Sounds good to me! Ok, thanks. I'll pick it up and route it through the proper channels. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org