The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	x86@linutronix.de, Masami Hiramatsu <mhiramat@kernel.org>,
	"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: Re: [WARNING] x86/mm: Found insecure W+X mapping at address ..
Date: Tue, 23 May 2017 18:35:19 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1705231822000.2740@nanos> (raw)
In-Reply-To: <CAGXu5jK-=c00ppm7h7ZgH7iVpRqRBLUQusYgm7yW4JDZ+r4RYw@mail.gmail.com>

On Tue, 23 May 2017, Kees Cook wrote:
> On Tue, May 23, 2017 at 8:40 AM, Thomas Gleixner <tglx@linutronix.de> 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

  reply	other threads:[~2017-05-23 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 15:40 [WARNING] x86/mm: Found insecure W+X mapping at address Thomas Gleixner
2017-05-23 15:54 ` Kees Cook
2017-05-23 16:35   ` Thomas Gleixner [this message]
2017-05-23 20:48     ` Thomas Gleixner
2017-05-23 22:59       ` Steven Rostedt
2017-05-24  6:20         ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1705231822000.2740@nanos \
    --to=tglx@linutronix.de \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=x86@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox