[Bug runtime/30415] conflicting types for ‘kallsyms_on_each_symbol’
wcohen at redhat dot com
sourceware-bugzilla@sourceware.org
Mon May 22 14:48:54 GMT 2023
https://sourceware.org/bugzilla/show_bug.cgi?id=30415
--- Comment #6 from William Cohen <wcohen at redhat dot com> ---
Did some kernel archeology. There are two kallsyms_on_each_symbol functions:
the kallsyms_on_each_symbol and another function
module_kallsyms_on_each_symbol. The initial kernel commit
75a66614db21007bcc8c37f9c5d5b922981387b9 has the kallsyms_on_each_symbol
iterate through the kernel symbols if there was no non-zero return from he
callback the module_kallsyms_on_each_symbol was run. The
module_kallsyms_on_each_symbol would invoke the callback for each symbol in
each module. There have been changes on the module_kallsyms_on_each_module as
now it takes an argument on which module's symbols to apply the callback to
(NULL could be passed in to get it to apply to all the modules). The module
argument was added by kernel git commit
07cc2c931e8e1083a31f4c51d2244fe264af63bf in Jan 2023.
The question is how to get stapkp_symbol_callback working without the struct
module argument.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Systemtap
mailing list