mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: bugzilla-daemon@bugzilla.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	bplant@iinet.net.au, Andrew Morton <akpm@linux-foundation.org>,
	mfasheh@suse.com, joel.becker@oracle.com
Subject: Re: [Bug 13631] BUG/panic - update_curr
Date: Sat, 04 Jul 2009 15:58:57 +0300	[thread overview]
Message-ID: <4A4F5211.10806@cs.helsinki.fi> (raw)
In-Reply-To: <200907031523.n63FN96i031564@demeter.kernel.org>

Hi Brad,

bugzilla-daemon@bugzilla.kernel.org wrote:
> --- Comment #14 from Brad Plant <bplant@iinet.net.au>  2009-07-03 15:23:06 ---
> Created an attachment (id=22193)
>  --> (http://bugzilla.kernel.org/attachment.cgi?id=22193)
> BUG kmalloc-16: Redzone overwritten
> 
> (In reply to comment #13)
>> Looking at the bug report, I'd be pretty surprised if this would be a
>> SLUB bug. It seems more likely that there's some memory corruption going
>> on under heavy load and SLAB just happens to have a different layout of
>> slab objects or something.
>>
>> Did you run the test with CONFIG_SLAB_DEBUG, btw?
> 
> I tried slub debugging first. I tried to make it crash for a while but of
> course it wouldn't do it when I wanted it to. I had given up on trying to crash
> slub and was just rebooting the node to change the kernel when I hit the
> jackpot.
> 
> Does this suggest ocfs2 is corrupting the memory?

Yup, that would be the prime suspect here. Lets cc ocfs2 developers and 
LKML. The corruption can be found here:

   http://bugzilla.kernel.org/attachment.cgi?id=22193

			Pekka

           reply	other threads:[~2009-07-04 13:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200907031523.n63FN96i031564@demeter.kernel.org>]

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=4A4F5211.10806@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=bplant@iinet.net.au \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=joel.becker@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.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

all inboxes | Powered by JetHome®