linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: Christoph Lameter <christoph@linuxfoundation.org>
Cc: "wfg@linux.intel.com" <wfg@linux.intel.com>,
	Christoph Lameter <cl@linux.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Early crashed kernel on CONFIG_SLOB
Date: Tue, 10 Jul 2012 22:45:57 +0300	[thread overview]
Message-ID: <CAOJsxLG7fWuHeh-KXzG1PHwZRWztQQYvmxgn_97aYBCtqrLWug@mail.gmail.com> (raw)
In-Reply-To: <CF1C132D-2873-408A-BCC9-B9F57BE6EDDB@linuxfoundation.org>

On Jul 10, 2012, at 6:17, wfg@linux.intel.com wrote:
>> This commit crashes the kernel w/o any dmesg output (the attached one
>> is created by the script as a summary for that run). This is very
>> reproducible in kvm for the attached config.
>>
>>        commit 3b0efdfa1e719303536c04d9abca43abeb40f80a
>>        Author: Christoph Lameter <cl@linux.com>
>>        Date:   Wed Jun 13 10:24:57 2012 -0500
>>
>>            mm, sl[aou]b: Extract common fields from struct kmem_cache

On Tue, Jul 10, 2012 at 9:37 PM, Christoph Lameter
<christoph@linuxfoundation.org> wrote:
> I sent a patch yesterday (or was it friday) to fix the issue. Sorry @airport right now.

Which patch is that? I can't seem to find it.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-07-10 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 11:17 wfg
2012-07-10 18:37 ` Christoph Lameter
2012-07-10 19:45   ` Pekka Enberg [this message]
2012-07-10 23:31   ` Christoph Lameter
2012-07-12  7:13     ` Pekka Enberg

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=CAOJsxLG7fWuHeh-KXzG1PHwZRWztQQYvmxgn_97aYBCtqrLWug@mail.gmail.com \
    --to=penberg@kernel.org \
    --cc=christoph@linuxfoundation.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wfg@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox