public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: xfs@oss.sgi.com
Subject: Re: Crash on 2.6.21.7 Vanilla + DRBD 0.7
Date: Fri, 5 Oct 2007 09:10:37 +1000	[thread overview]
Message-ID: <20071004231037.GJ23367404@sgi.com> (raw)
In-Reply-To: <20071004133302.GA5058@apartia.fr>

On Thu, Oct 04, 2007 at 03:33:02PM +0200, vindex+lists-xfs@apartia.org wrote:
> 
> Hi,
> 
> I did compile a fresh 2.6.21.7 kernel from kernel.org (no distro patch,
> ....), and latest svn (3062) 0.7.X drbd.
> 
> After just 2 days of uptime, I did experience another crash.
> 
> I wonder if it is an XFS related bug, a DRBD one, or related to XFS on
> top of DRBD.
> 
> This bug seems to occur with intensive IO operations.
> 
> What do you think about it ?
> 
> Thanks
> 
> 
> Oct  3 18:55:23  kernel: Oops: 0002 [#1]
> Oct  3 18:55:23  kernel: SMP 
> Oct  3 18:55:23  kernel: CPU:    7
> Oct  3 18:55:23  kernel: EIP:    0060:[<c016540c>]    Not tainted VLI
> Oct  3 18:55:23  kernel: EFLAGS: 00010046   (2.6.21-dl380-g5-20071001 #1)
> Oct  3 18:55:23  kernel: EIP is at cache_alloc_refill+0x11c/0x4f0

Use after free somewhere, i'd say. Turn on slab/slub poisoning and
other memory debugging options and see where it panics next
time.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

      parent reply	other threads:[~2007-10-04 23:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 13:33 Crash on 2.6.21.7 Vanilla + DRBD 0.7 vindex+lists-xfs
2007-10-04 14:27 ` Hannes Dorbath
2007-10-04 16:42   ` Laurent CARON
2007-10-04 14:35 ` Hannes Dorbath
2007-10-04 16:33   ` Laurent CARON
2007-10-10 15:15   ` Louis-David Mitterrand
2007-10-10 22:46     ` David Chinner
2007-10-11  7:36       ` Laurent CARON
2007-10-04 23:10 ` David Chinner [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=20071004231037.GJ23367404@sgi.com \
    --to=dgc@sgi.com \
    --cc=xfs@oss.sgi.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