No subject

[David Smith]

On Thu, Jul 27, 2017 at 9:47 AM, Eyal Yehuda via systemtap
<systemtap@sourceware.org> wrote:

... stuff deleted ...

> Please advice
> 1.
>  what should i do in addition to solve this issue as I must create an
> interaction between systemtap script and another kernel module
> 2.
>  In case this is not feasible can u please offer another alternative to
> make systemtap script use another kernel module services ?

I'm not 100% sure, but I believe you need to copy your module with
foo() to the /lib/modules/UNAME/kernel directory before trying to
build the systemtap module.

I don't think this really is a systemtap problem, I believe you'd have
the same problem with a 2nd kernel module that tried to access foo().

Give that a shot and let us know if this fixes your problem.

-- 
David Smith
Principal Software Engineer
Red Hat