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

2017-05-23 Thread Thomas Gleixner
On Tue, 23 May 2017, Steven Rostedt wrote: > On Tue, 23 May 2017 22:48:19 +0200 (CEST) > Thomas Gleixner 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

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

2017-05-23 Thread Steven Rostedt
On Tue, 23 May 2017 22:48:19 +0200 (CEST) Thomas Gleixner 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 introduct

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

2017-05-23 Thread Thomas Gleixner
On Tue, 23 May 2017, Thomas Gleixner wrote: > 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

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

2017-05-23 Thread Thomas Gleixner
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

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

2017-05-23 Thread Kees Cook
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

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

2017-05-23 Thread Thomas Gleixner
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. Thanks, tglx ---[ Modules ]--- 0xc