From: "Paweł Sikora" <pluto@agmk.net>
To: Neil Brown <neilb@suse.de>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
<linux-kernel@vger.kernel.org>, <akpm@linux-foundation.org>
Subject: Re: [2.6.37-rc8] BUG kmalloc-256: Poison overwritten.
Date: Fri, 31 Dec 2010 09:02:15 +0100 [thread overview]
Message-ID: <dfd5ffc181315d383c5d069c343b76af@agmk.net> (raw)
In-Reply-To: <20101231100012.3e6e3c1f@notabene.brown>
On Fri, 31 Dec 2010 10:00:12 +1100, Neil Brown <neilb@suse.de> wrote:
> Please report exactly which kernel you are running (git hash of head)
> and in
> particular whether
> commit 589a594be1fb8815b3f18e517be696c48664f728
>
> is present?
i'm testing the pure 2.6.37-rc8 which afaics contains mentioned merge:
3d0b608 589a594
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Dec 14 18:49:40 2010 -0800
Merge branch 'for-linus' of git://neil.brown.name/md
prev parent reply other threads:[~2010-12-31 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 15:08 [2.6.37-rc8] BUG kmalloc-256: Poison overwritten Pawel Sikora
2010-12-30 15:31 ` Pekka Enberg
2010-12-30 15:59 ` Pekka Enberg
2010-12-30 19:39 ` Paweł Sikora
2010-12-30 23:00 ` Neil Brown
2010-12-31 8:02 ` Paweł Sikora [this message]
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=dfd5ffc181315d383c5d069c343b76af@agmk.net \
--to=pluto@agmk.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=penberg@cs.helsinki.fi \
/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