From: "Zhang, Yanmin" <yanmin.zhang@intel.com>
To: "Mao, Bibo" <bibo.mao@intel.com>, <systemtap@sources.redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>
Subject: RE: module function probe
Date: Fri, 25 Nov 2005 06:14:00 -0000 [thread overview]
Message-ID: <8126E4F969BA254AB43EA03C59F44E8403FF5A24@pdsmsx404> (raw)
The module reference count is not correct. The module ref count should be increased with 1 when a kprobe is registered at the module exec text, and vice versa.
Yanmin
>>-----Original Message-----
>>From: Mao, Bibo
>>Sent: 2005年11月25日 13:50
>>To: systemtap@sources.redhat.com
>>Cc: 'Frank Ch. Eigler'; Keshavamurthy, Anil S; Zhang, Yanmin
>>Subject: module function probe
>>
>>Hi,
>> I wrote one module named probed.ko after compiled, and the other is kprobe
>>module named probing.ko which is to probe some function defined in probed.ko
>>module.
>> And then I executed the follow command so that some function can be probed.
>> #insmod probed.ko
>> #insmod probing.ko
>>But when I undelete module in such order kernel will crash
>> #rmmod probed.ko (system is ok)
>> #rmmod probing.ko (system will crash)
>>The reason is that when unregister kprobe it will restore original instruction,
>>but when probed module exits, its instruction address space is freed, so when
>>restore original instruction it will crash.
>>
>>Regards
>>Bibo,mao
next reply other threads:[~2005-11-25 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 6:14 Zhang, Yanmin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-30 22:00 Keshavamurthy, Anil S
2005-11-25 5:50 Mao, Bibo
2005-11-25 12:37 ` Frank Ch. Eigler
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=8126E4F969BA254AB43EA03C59F44E8403FF5A24@pdsmsx404 \
--to=yanmin.zhang@intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bibo.mao@intel.com \
--cc=fche@redhat.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).