Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934963Ab3DPSIs (ORCPT ); Tue, 16 Apr 2013 14:08:48 -0400 Received: from mail-ob0-f170.google.com ([209.85.214.170]:34352 "EHLO mail-ob0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934262Ab3DPSIq (ORCPT ); Tue, 16 Apr 2013 14:08:46 -0400 MIME-Version: 1.0 In-Reply-To: <1365797627-20874-1-git-send-email-keescook@chromium.org> References: <1365797627-20874-1-git-send-email-keescook@chromium.org> Date: Tue, 16 Apr 2013 11:08:42 -0700 X-Google-Sender-Auth: HpzL1yLBtwaTCfUybzj-NMhMl9w Message-ID: Subject: Re: [PATCH v2 0/6] kernel ASLR From: Kees Cook To: "H. Peter Anvin" Cc: LKML , "kernel-hardening@lists.openwall.com" , Thomas Gleixner , Ingo Molnar , "x86@kernel.org" , Jarkko Sakkinen , Matthew Garrett , Matt Fleming , Eric Northup , Dan Rosenberg , Julien Tinnes , Will Drewry , Kees Cook Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 789 Lines: 22 On Fri, Apr 12, 2013 at 1:13 PM, Kees Cook wrote: > This splits up the relocs tool changes into the separate logical pieces, > which should be easier to review. I could use some suggestions on a > better way to build it in the 4th patch. What I have now seems ugly, > but Kbuild would not give me its secrets. How does the relocation portion of this series look? It's separate from the ASLR logic, but required for it. Do those changes look good for the tip/kaslr tree? Thanks, -Kees -- Kees Cook Chrome OS Security -- 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/