From: "Theodore Ts'o" <tytso@mit.edu>
To: Gavin Guo <gavin.guo@canonical.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: commit 4066c33d0308f8 breaks booting under KVM
Date: Fri, 26 Jun 2015 23:49:10 -0400 [thread overview]
Message-ID: <20150627034910.GB474@thunk.org> (raw)
In-Reply-To: <20150626142332.GA28413@thunk.org>
On Fri, Jun 26, 2015 at 10:23:32AM -0400, Theodore Ts'o wrote:
> I can no longer boot Linus's tree under KVM using a 32-bit i386 build;
> it just hangs before any messages get sent to the serial console. It
> bisects down to:
>
> commit 4066c33d0308f87e9a3b0c7fafb9141c0bfbfa77
> Author: Gavin Guo <gavin.guo@canonical.com>
> Date: Wed Jun 24 16:55:54 2015 -0700
>
> mm/slab_common: support the slub_debug boot option on specific object size
> ...
As a follow up, this commit breaks 32-bit and 64-bit x86 if you have
CONFIG_SLAB enabled. When I switched to CONFIG_SLUB, the kernel
boots. So it appears this commit is breaking kernel configurations
with CONFIG_SLAB enabled.
- Ted
next prev parent reply other threads:[~2015-06-27 3:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 14:23 commit 4066c33d0308f8 breaks booting under KVM Theodore Ts'o
2015-06-27 3:49 ` Theodore Ts'o [this message]
[not found] ` <CA+55aFxxuf9=b_f_wPvnRs-oSCtG4vTCuELc9Vnxw=_87PxwSA@mail.gmail.com>
2015-06-29 14:01 ` Christoph Lameter
2015-06-29 14:28 ` [PATCH] Fix kmalloc slab creation sequence Christoph Lameter
2015-06-29 17:50 ` Linus Torvalds
2015-07-02 3:57 ` commit 4066c33d0308f8 breaks booting under KVM Gavin Guo
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=20150627034910.GB474@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=gavin.guo@canonical.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox