public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30415] conflicting types for ‘kallsyms_on_each_symbol’
Date: Mon, 22 May 2023 14:48:54 +0000	[thread overview]
Message-ID: <bug-30415-6586-ITObkOQkcI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30415-6586@http.sourceware.org/bugzilla/>

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.

  parent reply	other threads:[~2023-05-22 14:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  8:56 [Bug runtime/30415] New: " mcermak at redhat dot com
2023-05-03  9:01 ` [Bug runtime/30415] " mcermak at redhat dot com
2023-05-03 10:41 ` mcermak at redhat dot com
2023-05-09 19:23 ` wcohen at redhat dot com
2023-05-22  8:56 ` mcermak at redhat dot com
2023-05-22 14:01 ` wcohen at redhat dot com
2023-05-22 14:48 ` wcohen at redhat dot com [this message]
2023-05-24 11:16 ` mcermak at redhat dot com
2023-05-24 11:24 ` mcermak at redhat dot com
2023-05-25 18:43 ` wcohen at redhat dot com
2023-05-26 10:28 ` mcermak at redhat dot com
2023-05-30 14:51 ` mcermak at redhat dot com
2023-05-31 13:59 ` wcohen at redhat dot com
2023-06-02  9:28 ` mcermak at redhat dot com
2023-06-02 15:22 ` wcohen at redhat dot com
2023-06-02 18:26 ` mcermak at redhat dot com
2023-06-02 21:21 ` wcohen at redhat dot com
2023-06-02 21:38 ` mcermak at redhat dot com

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=bug-30415-6586-ITObkOQkcI@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /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).