Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754412AbaDXXqZ (ORCPT ); Thu, 24 Apr 2014 19:46:25 -0400 Received: from terminus.zytor.com ([198.137.202.10]:33724 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752714AbaDXXqY (ORCPT ); Thu, 24 Apr 2014 19:46:24 -0400 Message-ID: <5359A243.9010606@zytor.com> Date: Thu, 24 Apr 2014 16:46:11 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Kees Cook , Dave Young CC: LKML Subject: Re: kaslr should avoid setup_data region References: <20140424023544.GA2180@darkstar.nay.redhat.com> <20140424025016.GB2180@darkstar.nay.redhat.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/24/2014 03:50 PM, Kees Cook wrote: > Ah, it sounds like boot_params.hdr.setup_data contains a series of > e820-like entries chained together as a linked list? Which loaders > currently populate that? Looks like EFI? Seems like > arch/x86/boot/compressed/eboot.c works on setup_data at least. > > I won't be in a position to test EFI booting for a while. If someone > else took this, that would make it get fixed much faster. > > Do you have examples where this is actually causing failures? > > -Kees Syslinux can populate it with arbitrary data; in particular Syslinux uses it to pass FDT information if requested. -hpa -- 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/