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: Fri, 02 Jun 2023 15:22:29 +0000	[thread overview]
Message-ID: <bug-30415-6586-nqfouYkJDG@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 #14 from William Cohen <wcohen at redhat dot com> ---
Hi Martin,
The patch is looking pretty good.  There are just a few minor comments I have
on it.

One concern have is if RHEL backport some of the live patching support
to RHEL kernel the kernel version checks might not catch that.
However, probably better to just use the kernel version as currently
done and fix the problem with autoconf check if/when RHEL backports
patches.


Is there a need for both stapkp_kernel_symbol_callback and
stapkp_module_symbol_callback?  in kprobes.c?  They look the same with
the exception of the function name.  It would simplfy the code if
those were combined into a single function.


In runtime/linux/kprobe.c have:

extern void *_stp_module_kallsyms_on_each_symbol;

However, its static in runtime/linux/runtime.h:

static void *_stp_module_kallsyms_on_each_symbol;

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

  parent reply	other threads:[~2023-06-02 15:22 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
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 [this message]
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-nqfouYkJDG@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).