linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@cse.unsw.edu.au>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm4
Date: Thu, 5 Jun 2003 11:53:51 +1000	[thread overview]
Message-ID: <16094.41647.614418.452777@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Helge Hafting on Wednesday June 4

On Wednesday June 4, helgehaf@aitel.hist.no wrote:
> Raid-1 seems to work in 2.5.70-mm4, but raid-0 still fail.
> 
> Trying to boot with raid-0 autodetect yields a long string of:
> Slab error in cache_free_debugcheck
> cache 'size-32' double free or
> memory after object overwritten.
> (Is this something "Page alloc debugging"may be used for?)
> kfree+0xfc/0x330
> raid0_run
> raid0_run
> printk
> blk_queue_make_request
> do_md_run
> md_ioctl
> dput
> blkdev_ioctl
> sys_ioctl
> syscall_call
> 
> I get a ton of these, in between normal
> initialization messages.  Then the thing
> dies with a panic due to exception in interrupt.
> 
> This is a monolithic smp preempt kernel on a dual celeron.
> The disks are scsi, the filesystems ext2.  There is one
> raid-0 array and two raid-1 arrays, as well as some
> ordinary partitions.  Root is on raid-1.
> 
> Helge Hafting

grrr... I thought I had that right...

You need to remove the two calls to 'kfree' at the end of 
create_strip_zones.

I have jsut sent some patches to Linus (and linux-raid@vger) which
will update his tree to include this fix.

NeilBrown
--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2003-06-05  1:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04  6:18 2.5.70-mm4 Andrew Morton
2003-06-04  8:12 ` 2.5.70-mm4 RAID1 seems to work! Helge Hafting
2003-06-04 13:55 ` 2.5.70-mm4 Paul Larson
2003-06-04 15:33 ` 2.5.70-mm4 Paul Larson
2003-06-04 15:52 ` 2.5.70-mm4 Paul Larson
2003-06-04 18:00   ` 2.5.70-mm4 Felipe Alfaro Solana
2003-06-04 17:14 ` 2.5.70-mm4 Alexander Hoogerhuis
2003-06-04 21:12 ` 2.5.70-mm4 Helge Hafting
2003-06-05  1:53   ` Neil Brown [this message]
2003-06-05 15:24     ` 2.5.70-mm4 this helped but still no raid0 Helge Hafting
2003-06-04 21:33 ` 2.5.70-mm4 Rudmer van Dijk
2003-06-05  9:21   ` 2.5.70-mm4 Maciej Soltysiak

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=16094.41647.614418.452777@notabene.cse.unsw.edu.au \
    --to=neilb@cse.unsw.edu.au \
    --cc=akpm@digeo.com \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox