All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Lameter <cl@linux.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: kernel test robot <xiaolong.ye@intel.com>,
	Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
	Borislav Petkov <bp@alien8.de>, Brian Gerst <brgerst@gmail.com>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Jiri Slaby <jslaby@suse.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mike Galbraith <efault@gmx.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org, linux-mm@kvack.org, Pekka Enberg <penberg@kernel.org>,
	David Rientjes <rientjes@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [lkp-robot] [x86/kconfig]  81d3871900: BUG:unable_to_handle_kernel
Date: Fri, 13 Oct 2017 10:22:54 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.20.1710131021240.3949@nuc-kabylake> (raw)
In-Reply-To: <20171013044521.662ck56gkwaw3xog@treble>

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.

WARNING: multiple messages have this Message-ID (diff)
From: Christopher Lameter <cl@linux.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel
Date: Fri, 13 Oct 2017 10:22:54 -0500	[thread overview]
Message-ID: <alpine.DEB.2.20.1710131021240.3949@nuc-kabylake> (raw)
In-Reply-To: <20171013044521.662ck56gkwaw3xog@treble>

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

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.


  parent reply	other threads:[~2017-10-13 15:23 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 12:15 [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel kernel test robot
2017-10-10 12:15 ` kernel test robot
2017-10-11  2:31 ` Josh Poimboeuf
2017-10-11  2:31   ` Josh Poimboeuf
2017-10-11  2:31   ` Josh Poimboeuf
2017-10-11 17:01   ` Josh Poimboeuf
2017-10-11 17:01     ` Josh Poimboeuf
2017-10-11 17:01     ` Josh Poimboeuf
2017-10-12 17:05     ` Christopher Lameter
2017-10-12 17:05       ` Christopher Lameter
2017-10-12 17:54       ` Linus Torvalds
2017-10-12 17:54         ` Linus Torvalds
2017-10-12 17:54         ` Linus Torvalds
2017-10-12 18:48         ` Andrew Morton
2017-10-12 18:48           ` Andrew Morton
2017-10-12 18:48           ` Andrew Morton
2017-10-12 19:19           ` Geert Uytterhoeven
2017-10-12 19:19             ` Geert Uytterhoeven
2017-10-12 19:19             ` Geert Uytterhoeven
2017-10-12 17:54       ` Linus Torvalds
2017-10-12 17:54         ` Linus Torvalds
2017-10-12 17:54         ` Linus Torvalds
2017-10-13  4:45       ` Josh Poimboeuf
2017-10-13  4:45         ` Josh Poimboeuf
2017-10-13  4:45         ` Josh Poimboeuf
2017-10-13 13:56         ` Andrey Ryabinin
2017-10-13 13:56           ` Andrey Ryabinin
2017-10-13 13:56           ` Andrey Ryabinin
2017-10-13 16:19           ` Josh Poimboeuf
2017-10-13 16:19             ` Josh Poimboeuf
2017-10-13 16:19             ` Josh Poimboeuf
2017-10-13 19:09           ` Linus Torvalds
2017-10-13 19:09             ` Linus Torvalds
2017-10-13 19:09             ` Linus Torvalds
2017-10-13 19:09             ` Linus Torvalds
2017-10-13 20:01             ` Andy Lutomirski
2017-10-13 20:01               ` Andy Lutomirski
2017-10-13 20:01               ` Andy Lutomirski
2017-10-13 20:01               ` Andy Lutomirski
2017-10-13 20:17             ` Jeffrey Walton
2017-10-13 20:17               ` Jeffrey Walton
2017-10-13 20:17               ` Jeffrey Walton
2017-10-13 15:22         ` Christopher Lameter [this message]
2017-10-13 15:22           ` Christopher Lameter
2017-10-13 15:37           ` Josh Poimboeuf
2017-10-13 15:37             ` Josh Poimboeuf
2017-10-13 15:37             ` Josh Poimboeuf
2017-10-17  7:33     ` Joonsoo Kim
2017-10-17  7:33       ` Joonsoo Kim
2017-10-17  7:33       ` Joonsoo Kim
2017-10-17  7:50       ` Thomas Gleixner
2017-10-17  7:50         ` Thomas Gleixner
2017-10-17  7:50         ` Thomas Gleixner
2017-10-18  7:31         ` Joonsoo Kim
2017-10-18  7:31           ` Joonsoo Kim
2017-10-18  7:31           ` Joonsoo Kim
2017-10-18 10:40       ` Linus Torvalds
2017-10-18 10:40         ` Linus Torvalds
2017-10-18 10:40         ` Linus Torvalds
2017-10-18 13:15         ` Thomas Gleixner
2017-10-18 13:15           ` Thomas Gleixner
2017-10-18 13:15           ` Thomas Gleixner
2017-10-19  2:14           ` Joonsoo Kim
2017-10-19  2:14             ` Joonsoo Kim
2017-10-19  2:14             ` Joonsoo Kim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1710131021240.3949@nuc-kabylake \
    --to=cl@linux.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dvlasenk@redhat.com \
    --cc=efault@gmx.de \
    --cc=hpa@zytor.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jpoimboe@redhat.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@01.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=xiaolong.ye@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.