From: NeilBrown <neilb@suse.de>
To: "Mo, Moore" <Moore.Mo@Polycom.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Kernel crash at md_seq_show of drivers/md/md.c
Date: Thu, 16 May 2013 11:19:05 +1000 [thread overview]
Message-ID: <20130516111905.671d02ff@notabene.brown> (raw)
In-Reply-To: <74AD8F6BA17DDA4EBE980849BC39C00D02803790@HKGMBOXPRD22.polycom.com>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Wed, 15 May 2013 20:11:52 +0800 "Mo, Moore" <Moore.Mo@Polycom.com> wrote:
> Dear Neil,
>
> Thank you for your clue. I make deeper trace after that and found another suspicion point. Kernel maybe wakeup a mdk_thread which was kfree in failed case of mddev->pers->run(mddev).
>
> For make sure my guess, I add some printk in order to get more info. It seems that md_seq_show try to wake up a mdk_thread in mddev_unlock() before md_seq_show return, but the thread was kfree already by "out_free_conf" case of run() function in drivers/md/raid10.c.
>
> The Oops report as attached.
>
I don't really have time for bug reports against ancient kernels - sorry.
If you think you've found a bug, please at least look in the current mainline
kernel to see if the code has changed, and preferably reproduce against the
current mainline kernel.
In this case the bug was fixed by commit
01f96c0a9922cd9919baf9d16febdf7016177a12
18 months ago (linux 3.1).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-05-16 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 12:11 Kernel crash at md_seq_show of drivers/md/md.c Mo, Moore
2013-05-16 1:19 ` NeilBrown [this message]
2013-05-16 12:35 ` Mo, Moore
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=20130516111905.671d02ff@notabene.brown \
--to=neilb@suse.de \
--cc=Moore.Mo@Polycom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.