From: Pekka Enberg <penberg@iki.fi>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Meelis Roos <mroos@linux.ee>, Pekka Enberg <penberg@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
Matt Mackall <mpm@selenic.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: Slab BUG with DEBUG_* options
Date: Tue, 03 Dec 2013 14:44:31 +0200 [thread overview]
Message-ID: <529DD22F.3040102@iki.fi> (raw)
In-Reply-To: <CAAmzW4N=2--OuOFVEME3FJa7uFCkVEYJp=9DbSBVOPjiXnLxcg@mail.gmail.com>
On 12/03/2013 02:25 PM, Joonsoo Kim wrote:
> No. He report that BUG() is triggered on v3.11-rc2 and v3.12.
> And my recent change is merged into v3.13-rc1 as you know. :)
Hah, I guess my eyesight isn't what it used to be, I could have sworn it
said v3.13-rc2... Thanks anyway, Joonsoo!
Pekka
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Pekka Enberg <penberg@iki.fi>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Meelis Roos <mroos@linux.ee>, Pekka Enberg <penberg@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
Matt Mackall <mpm@selenic.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: Slab BUG with DEBUG_* options
Date: Tue, 03 Dec 2013 14:44:31 +0200 [thread overview]
Message-ID: <529DD22F.3040102@iki.fi> (raw)
In-Reply-To: <CAAmzW4N=2--OuOFVEME3FJa7uFCkVEYJp=9DbSBVOPjiXnLxcg@mail.gmail.com>
On 12/03/2013 02:25 PM, Joonsoo Kim wrote:
> No. He report that BUG() is triggered on v3.11-rc2 and v3.12.
> And my recent change is merged into v3.13-rc1 as you know. :)
Hah, I guess my eyesight isn't what it used to be, I could have sworn it
said v3.13-rc2... Thanks anyway, Joonsoo!
Pekka
next prev parent reply other threads:[~2013-12-04 20:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 11:42 Slab BUG with DEBUG_* options Meelis Roos
2013-11-30 11:42 ` Meelis Roos
2013-11-30 22:31 ` David Rientjes
2013-11-30 22:31 ` David Rientjes
2013-12-02 19:02 ` Christoph Lameter
2013-12-02 19:02 ` Christoph Lameter
2013-12-03 8:46 ` Meelis Roos
2013-12-03 8:46 ` Meelis Roos
2013-12-03 9:17 ` Meelis Roos
2013-12-03 9:17 ` Meelis Roos
2013-12-03 11:53 ` Pekka Enberg
2013-12-03 11:53 ` Pekka Enberg
2013-12-03 12:25 ` Joonsoo Kim
2013-12-03 12:25 ` Joonsoo Kim
2013-12-03 12:44 ` Pekka Enberg [this message]
2013-12-03 12:44 ` Pekka Enberg
2013-12-03 15:46 ` Christoph Lameter
2013-12-03 15:46 ` Christoph Lameter
2013-12-03 20:33 ` Meelis Roos
2013-12-03 20:33 ` Meelis Roos
2013-12-03 20:59 ` Christoph Lameter
2013-12-03 20:59 ` Christoph Lameter
[not found] ` <alpine.DEB.2.02.1312030930450.4115@gentwo.org>
2013-12-03 20:25 ` Christoph Lameter
2013-12-03 20:25 ` Christoph Lameter
2013-12-03 21:18 ` Meelis Roos
2013-12-03 21:18 ` Meelis Roos
2013-12-03 21:58 ` Christoph Lameter
2013-12-03 21:58 ` Christoph Lameter
2013-12-08 15:00 ` Meelis Roos
2013-12-08 15:00 ` Meelis Roos
2013-12-08 15:00 ` Meelis Roos
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=529DD22F.3040102@iki.fi \
--to=penberg@iki.fi \
--cc=cl@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=mroos@linux.ee \
--cc=penberg@kernel.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 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.