On Fri, Oct 13, 2017 at 10:22:54AM -0500, Christopher Lameter wrote: > On Thu, 12 Oct 2017, Josh Poimboeuf wrote: > > > > Can you run SLUB with full debug? specify slub_debug on the commandline or > > > set CONFIG_SLUB_DEBUG_ON > > > > Oddly enough, with CONFIG_SLUB+slub_debug, I get the same crypto panic I > > got with CONFIG_SLOB. The trapping instruction is: > > > > vmovdqa 0x140(%rdi),%xmm0 > > > > I'll try to bisect it tomorrow. It at least goes back to v4.10. I'm > > not really sure whether this panic is related to SLUB or SLOB at all. > > Guess not. The slab allocators can fail if the metadata gets corrupted. > That is why we have extensive debug modes so we can find who is to blame > for corruptions. > > > (Though the original panic reported upthread by the kernel test robot > > *does* look SLOB related.) > > Yup. Just happened to be configured for SLOB then.
Just to clarify, the upthread panic in SLOB is *not* related to the crypto issue. So somebody still needs to look at that one: https://lkml.kernel.org/r/20171010121513.GC5445@yexl-desktop -- Josh
