Re: [WARNING] x86/mm: Found insecure W+X mapping at address ..

From	Thomas Gleixner <tglx@linutronix.de>
Newsgroups	linux.kernel
Subject	Re: [WARNING] x86/mm: Found insecure W+X mapping at address ..
Date	2017-05-24 08:30 +0200
Message-ID	<tKxXY-71C-17@gated-at.bofh.it> (permalink)
References	<tKkem-58v-23@gated-at.bofh.it> <tKko1-5cc-1@gated-at.bofh.it> <tKl0L-5Ft-35@gated-at.bofh.it> <tKoUI-8uq-61@gated-at.bofh.it> <tKqWu-1xx-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, 23 May 2017, Steven Rostedt wrote:

> On Tue, 23 May 2017 22:48:19 +0200 (CEST)
> Thomas Gleixner <tglx@linutronix.de> wrote:
> 
> 
> > It's not KPROBES, it's the new fangled ftrace trampoline code. I
> > added a few printks. All the leaked W+X mappings are allocated via
> > this callchain:
> 
> The trampoline code isn't new. But it has new users because of the
> introduction to synchronize_rcu_tasks(), and there was a bug I fixed in
> -rc2 that moved it down because the test was run before
> synchronize_rcu_tasks() was functional.
> 
> Is this still a bug in rc2?

Yes. Otherwise we wouldn't talking about.

Thanks,

	tglx

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[WARNING] x86/mm: Found insecure W+X mapping at address .. Thomas Gleixner <tglx@linutronix.de> - 2017-05-23 17:50 +0200
  Re: [WARNING] x86/mm: Found insecure W+X mapping at address .. Kees Cook <keescook@chromium.org> - 2017-05-23 18:00 +0200
    Re: [WARNING] x86/mm: Found insecure W+X mapping at address .. Thomas Gleixner <tglx@linutronix.de> - 2017-05-23 18:40 +0200
      Re: [WARNING] x86/mm: Found insecure W+X mapping at address .. Thomas Gleixner <tglx@linutronix.de> - 2017-05-23 22:50 +0200
        Re: [WARNING] x86/mm: Found insecure W+X mapping at address .. Steven Rostedt <rostedt@goodmis.org> - 2017-05-24 01:00 +0200
          Re: [WARNING] x86/mm: Found insecure W+X mapping at address .. Thomas Gleixner <tglx@linutronix.de> - 2017-05-24 08:30 +0200

csiph-web