From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967595AbdEWQfX (ORCPT ); Tue, 23 May 2017 12:35:23 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:55252 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967530AbdEWQfW (ORCPT ); Tue, 23 May 2017 12:35:22 -0400 Date: Tue, 23 May 2017 18:35:19 +0200 (CEST) From: Thomas Gleixner To: Kees Cook cc: LKML , x86@linutronix.de, Masami Hiramatsu , "Luis R. Rodriguez" Subject: Re: [WARNING] x86/mm: Found insecure W+X mapping at address .. In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) 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, 23 May 2017, Kees Cook wrote: > On Tue, May 23, 2017 at 8:40 AM, Thomas Gleixner wrote: > > As of 4.12-rc1 one of my machines triggers the insecure W+X mapping. > > > It's consistenly 9 entries close to the beginning of the module space, > > before the first actual module starts. See below. > > > > Any ideas which avoid bisecting would be appreciated. > > Is this the same as: > > https://lkml.org/lkml/2017/5/19/899 > > ? > > The location is very similar. CONFIG_KPROBES_SANITY_TEST=n does not make it go away, but I suspect it's something in that area, as I recently switched on all of these self tests. I'll dig into it later today. Need to walk the dogs first. Thanks, tglx