From: "NeilBrown" <neilb@suse.de>
To: Gabriele Tozzi <gabriele@tozzi.eu>
Cc: linux-raid@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Kernel bug?
Date: Sun, 5 Apr 2009 08:40:04 +1000 (EST) [thread overview]
Message-ID: <b4d41c1ac8bd783b1a62b73b4efc4200.squirrel@neil.brown.name> (raw)
In-Reply-To: <49D777BC.4090009@tozzi.eu>
On Sun, April 5, 2009 1:07 am, Gabriele Tozzi wrote:
> Hello,
>
> I guess I've found a kernel bug: I get an oops when rebuilding a raid1
> array (/dev/md5) on an SMP system. The md5_resync process then hangs.
Yes, it appears you have found a bug. Thanks for reporting it.
It looks like an alloc_page failed in r1buf_pool_alloc and when trying
to clean up we tried to free pages that had never been allocated.
The code in raid1.c assumes that newly allocated 'bios' have their
bvec initialised to NULLs, but that apparently changed recently
with commit d3f761104b097738932afcc310fbbbbfb007ef92
I'll post a patch after the weekend.
Thanks,
NeilBrown
next prev parent reply other threads:[~2009-04-04 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 15:07 Kernel bug? Gabriele Tozzi
2009-04-04 22:40 ` NeilBrown [this message]
2009-04-06 4:43 ` Neil Brown
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=b4d41c1ac8bd783b1a62b73b4efc4200.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=gabriele@tozzi.eu \
--cc=jens.axboe@oracle.com \
--cc=linux-raid@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).