This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/6427] New: -DRELAY_HOST/RELAY_GUEST taints the kernel
- From: "mhiramat at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 17 Apr 2008 16:33:13 -0000
- Subject: [Bug runtime/6427] New: -DRELAY_HOST/RELAY_GUEST taints the kernel
- Reply-to: sourceware-bugzilla at sourceware dot org
I've gotten 'kernel tainted' message when using RELAY_HOST and RELAY_GUEST modules.
I ran below commands.
-----
$ stap -m host -e 'probe begin{print("hello ")}' -DRELAY_HOST=test1
^\
$ stap -m guest -e 'probe begin{print("hello ")}' -DRELAY_GUEST=test1
-----
And I got below messages.
--(dmesg)--
host: systemtap: 0.7/0.131, base: ffffffff885c8000, memory:
498072+28032+448+14000 data+text+ctx+net, probes: 1
guest: no version for "stp_print_flush_test1" found: kernel tainted.
guest: systemtap: 0.7/0.131, base: ffffffff8864a000, memory:
497488+27848+448+14000 data+text+ctx+net, probes: 1
---------
I guess that this comes from there is no entry of stp_print_flush_test1 in
"Module.symver"s which are used when building the guest module.
If so, we need to find that how to tell the version of the exported symbol of a
host module to a guest module.
one possible solution is keeping Module.symver file which is made when building
a host module, and pass it when building guest module by a new option.
--
Summary: -DRELAY_HOST/RELAY_GUEST taints the kernel
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mhiramat at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6427
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.