[Bug runtime/30415] conflicting types for ‘kallsyms_on_each_symbol’

mcermak at redhat dot com sourceware-bugzilla@sourceware.org
Fri May 26 10:28:23 GMT 2023


https://sourceware.org/bugzilla/show_bug.cgi?id=30415

--- Comment #10 from Martin Cermak <mcermak at redhat dot com> ---
Gotcha (probably ;) so since module_kallsyms_on_each_symbol() isn't exported
just like kallsyms_on_each_symbol() isn't, and since starting from kernel
commit 013c1667cf78c1d847152f7116436d82dcab3db4
module_kallsyms_on_each_symbol() isn't called from kallsyms_on_each_symbol(),
we basically need to duplicate most of the kallsyms_on_each_symbol() related
logic (mostly in runtime/ and staprun/) in order to tap
module_kallsyms_on_each_symbol() just like kallsyms_on_each_symbol() is tapped
(via send_a_relocation() in staprun)..

Not sure yet what to do about the non-uniqueness of the symbols, but I assume
this is not a new problem, so something in the existing code needs to already
address this to some extent, and the new code can follow that model..

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Systemtap mailing list