From: "Yu-Chen Wu" <g944370@oz.nthu.edu.tw>
To: "'Neil Brown'" <neilb@suse.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-raid@vger.kernel.org>
Subject: RE: Could "bio_vec" be referenced any time?
Date: Wed, 7 Feb 2007 20:20:42 +0800 [thread overview]
Message-ID: <009601c74ab2$6330b8c0$0100a8c0@sslabmayasky> (raw)
In-Reply-To: <17864.56037.855359.839197@notabene.brown>
Hi NeilBrown,
Thank you for your help and introducing "ksymoops" to me.
I think you are right.
The BIO is passed by MD put BIO into a share "kfifo".
THX : )
-----Original Message-----
From: linux-raid-owner@vger.kernel.org
[mailto:linux-raid-owner@vger.kernel.org] On Behalf Of Neil Brown
Sent: Wednesday, February 07, 2007 3:46 AM
To: Yu-Chen Wu
Cc: linux-kernel@vger.kernel.org; linux-raid@vger.kernel.org
Subject: Re: Could "bio_vec" be referenced any time?
On Tuesday February 6, g944370@oz.nthu.edu.tw wrote:
> Hi all,
> I write a module that creates a kernel thread to show the BIOs from
> MD modules.
> The kernel thread will call show_bio() when md passing a BIO to my
> module,else sleep.
> Sometimes, show_bio() continues working successfully ,but it
> somtimes makes "general protection fault".
> The show_bio() always works when I comment the
> "bio_for_each_segment" loop.
> Is the zone I comment the cause of the fault?
> As above, I consider it's the main problem.Also, I strongly want to
> know your opinions.Thank you for help.
>
> THX
Without seeing how the bio gets to show_bio it is hard to be certain,
but my guess would be that by the time show_bio tries to inspect the
bio, the IO request involving it has already completed and the bio has
been freed, so you are accessing freed memory.
> Feb 6 22:00:28 RAID-SUSE kernel: Code: 8b 00 f6 c4 08 74 0e 48 c7 c7 14
9c
> 45 88 31 c0 e8 b5 bf e2
If you feed this line into ksymoops you get:
Code; 0000000000000000 Before first symbol
0: 8b 00 mov (%rax),%eaxC
...
so it is trying to dereference $rax.
> Feb 6 22:00:28 RAID-SUSE kernel: RAX: 6b6b6b6b6b6b6b6b RBX:
> ffff810037f52668 RCX: 0000000000040000
Which contains 6b6b6b6b6b6b6b6b.
which is lots of copies of 'POISON_FREE' (defined in
include/linux/poison.h) which makes it really look like that memory
has already been freed.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-02-07 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 15:17 Could "bio_vec" be referenced any time? Yu-Chen Wu
2007-02-06 19:45 ` Neil Brown
2007-02-07 12:20 ` Yu-Chen Wu [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='009601c74ab2$6330b8c0$0100a8c0@sslabmayasky' \
--to=g944370@oz.nthu.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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