From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758215AbdJMPXB (ORCPT ); Fri, 13 Oct 2017 11:23:01 -0400 Received: from resqmta-ch2-03v.sys.comcast.net ([69.252.207.35]:59628 "EHLO resqmta-ch2-03v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753538AbdJMPW6 (ORCPT ); Fri, 13 Oct 2017 11:22:58 -0400 Date: Fri, 13 Oct 2017 10:22:54 -0500 (CDT) From: Christopher Lameter X-X-Sender: cl@nuc-kabylake To: Josh Poimboeuf cc: kernel test robot , Ingo Molnar , Andy Lutomirski , Borislav Petkov , Brian Gerst , Denys Vlasenko , "H. Peter Anvin" , Jiri Slaby , Linus Torvalds , Mike Galbraith , Peter Zijlstra , Thomas Gleixner , LKML , lkp@01.org, linux-mm@kvack.org, Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton Subject: Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel In-Reply-To: <20171013044521.662ck56gkwaw3xog@treble> Message-ID: References: <20171010121513.GC5445@yexl-desktop> <20171011023106.izaulhwjcoam55jt@treble> <20171011170120.7flnk6r77dords7a@treble> <20171013044521.662ck56gkwaw3xog@treble> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-CMAE-Envelope: MS4wfNf1pR9OY/am/yFAeZvxMj1hRoJaefJC5B93PMzDslGOdBQ163+fM+5la+vWxRYirYV5FoAaghE9/G95BkdV5IwOITZObFK3XmMIy38a6s2Qim9rDxKJ MA8AmR2kC7YzvjQmkmPWjhhhyXiwmoAWQU6pdai4HBKLopogx13/6VIQfPX+SGQ6R4LbRgYo8FcfcNHuGbHxGfBOZefFIE8XuDC+KoCXXdf/b17gWlH52tJX q4vBs84ABsXUkaI8HkRJB9D96G8h3iiHRN9G7ymKnIPzq8CRIKih23LwZlntCzTnTb4/QGiO5mD/FWwY8solwCY7vTG8M7VZxAIDX+U1evmOlqIifT5hk7cX a90TMb04iJq7zVB/tO/2YN8mnAcdYv2wdr6rcmOWTUihF72aflNw5fnsMrdWrC9CF1HKvHjHo71MixgUIx4gPoc+gUskGinm5Rad9rdRtuoFihLlXdjYSYoD WGfzgXYRMAzTh8fDmIGaS0qUt82hqcJnnqrQjPkXK5CnQGnO71cbFD++sXDKVAvW2/Q6lQ+tsBG26yDFKQuP27aEf25L9+CVsTrckW/g2ZlNTj1uShe7/dZg tqm8lNwPvTTgZGCyon9fSltrmkZaG31+gECDrFdvmHRp3KkK2UyCeTdK+3SoboD4NUNDoXCx4E7eFfzwA1sKmePPP0ASDt8Zbu+iBRlTPv5fZHrGonYBajLG 16OirraWgJ4= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.