Thread (28 messages) 28 messages, 7 authors, 2015-08-05

Re: unable to handle kernel NULL pointer dereference on 3.18.13-rt10

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2015-07-24 19:22:03

On Fri, 24 Jul 2015 21:02:26 +0200 (CEST)
Thomas Gleixner [off-list ref] wrote:
On Wed, 22 Jul 2015, Steven Rostedt wrote:
quoted
It's still there. Note, that when I pull -rt into stable, I do a
 git quiltimport, which renames the patch set. It's now called:

 0089-slub-delay-ctor-until-the-object-is-requested.patch
quoted
From the 4.0.8-rt6 announce:
- The delayed kmem_cache constructor caused problems. Steven Rostedt
  reported problems versus the signal handling code and Koehrer
  Mathias reported the same. The patch in question has been reverted
  and a patch currently sitting in -mm has been added which provides
  the same functionality (running the constructor with enabled
  interrupts). Patch provided by Thomas Gleixner. 

The stable trees which carry the delay-ctor patches should be updated
to this.

Reverting the patch at least prevents the BUG. Latencywise the slub patch

   mm-slub-move-slab-initialization-into-irq-enabled-re.patch

is the one which wants to be ported back.
OK, thanks.

Just to let people know. I'm going to be traveling next week and when I
get back in August, my top priority is to work on the stable patches.
For 3.18, I'll be looking at the patches that have been emailed to the
list, and I want to fix NO_HZ for 3.10-3.14.

I'll be also looking at the patches in the latest development RT
release that needs to be backported.

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help