From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758166AbdJMPhl (ORCPT ); Fri, 13 Oct 2017 11:37:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51158 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753545AbdJMPhk (ORCPT ); Fri, 13 Oct 2017 11:37:40 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 0E85C3E2C2 Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=jpoimboe@redhat.com Date: Fri, 13 Oct 2017 10:37:35 -0500 From: Josh Poimboeuf To: Christopher Lameter 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 Message-ID: <20171013153735.yywauekabxnczg74@treble> References: <20171010121513.GC5445@yexl-desktop> <20171011023106.izaulhwjcoam55jt@treble> <20171011170120.7flnk6r77dords7a@treble> <20171013044521.662ck56gkwaw3xog@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Fri, 13 Oct 2017 15:37:40 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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