From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30415] New: conflicting types for ‘kallsyms_on_each_symbol’
Date: Wed, 03 May 2023 08:56:42 +0000 [thread overview]
Message-ID: <bug-30415-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30415
Bug ID: 30415
Summary: conflicting types for ‘kallsyms_on_each_symbol’
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
Following is one of the problems CI gating shows for systemtap-4.9-1.fc39:
[root@rawh ~]# uname -r; rpm -q systemtap
6.4.0-0.rc0.20230428git33afd4b76393.7.fc39.x86_64
systemtap-4.9-1.fc39.x86_64
[root@rawh ~]#
[root@rawh ~]#
[root@rawh ~]# stap -vp4 -e 'probe nfsd.close? { printf("%s\n", filename) }
probe never { exit() }'
Pass 1: parsed user script and 484 library scripts using
124832virt/101128res/11136shr/89524data kb, in 180usr/40sys/219real ms.
Pass 2: analyzed script: 1 probe, 1 function, 0 embeds, 0 globals using
213068virt/193116res/14828shr/177760data kb, in 2040usr/430sys/2487real ms.
Pass 3: translated to C into
"/tmp/stapcVlKLM/stap_9691453a981c3fed6300ada89e578986_1302_src.c" using
213068virt/193244res/14956shr/177760data kb, in 0usr/0sys/0real ms.
In file included from /usr/local/share/systemtap/runtime/linux/runtime.h:288,
from /usr/local/share/systemtap/runtime/runtime.h:26,
from
/tmp/stapcVlKLM/stap_9691453a981c3fed6300ada89e578986_1302_src.c:21:
/usr/local/share/systemtap/runtime/sym.c:1159:5: error: conflicting types for
‘kallsyms_on_each_symbol’; have ‘int(int (*)(void *, const char *, struct
module *, long unsigned int), void *)’
1159 | int kallsyms_on_each_symbol(int (*fn)(void *, const char *, struct
module *,
| ^~~~~~~~~~~~~~~~~~~~~~~
In file included from ./include/linux/ftrace.h:13,
from ./include/linux/kprobes.h:28,
from /usr/local/share/systemtap/runtime/linux/runtime.h:21:
./include/linux/kallsyms.h:70:5: note: previous declaration of
‘kallsyms_on_each_symbol’ with type ‘int(int (*)(void *, const char *, long
unsigned int), void *)’
70 | int kallsyms_on_each_symbol(int (*fn)(void *, const char *, unsigned
long),
| ^~~~~~~~~~~~~~~~~~~~~~~
/usr/local/share/systemtap/runtime/sym.c: In function
‘kallsyms_on_each_symbol’:
/usr/local/share/systemtap/runtime/sym.c:1166:85: error: passing argument 1 of
‘(int (*)(int (*)(void *, const char *, long unsigned int), void
*))_stp_kallsyms_on_each_symbol’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
1166 | return (*
(kallsyms_on_each_symbol_fn)_stp_kallsyms_on_each_symbol)(fn, data);
|
^~
|
|
|
int (*)(void *, const char *, struct module *, long unsigned int)
/usr/local/share/systemtap/runtime/sym.c:1166:85: note: expected ‘int (*)(void
*, const char *, long unsigned int)’ but argument is of type ‘int (*)(void *,
const char *, struct module *, long unsigned int)’
In file included from ./include/linux/kernel.h:30,
from ./arch/x86/include/asm/percpu.h:27,
from ./arch/x86/include/asm/preempt.h:6,
from ./include/linux/preempt.h:78,
from ./include/linux/spinlock.h:56,
from ./include/linux/mmzone.h:8,
from ./include/linux/gfp.h:7,
from
/usr/local/share/systemtap/runtime/linux/runtime_defines.h:20,
from /usr/local/share/systemtap/runtime/runtime_defines.h:8,
from
/tmp/stapcVlKLM/stap_9691453a981c3fed6300ada89e578986_1302_src.c:12:
/usr/local/share/systemtap/runtime/linux/print.c: In function
‘_stp_print_kernel_info’:
/usr/local/share/systemtap/runtime/linux/print.c:365:43: error: ‘struct module’
has no member named ‘module_core’
365 | (unsigned long) THIS_MODULE->module_core,
| ^~
./include/linux/printk.h:427:33: note: in definition of macro
‘printk_index_wrap’
427 | _p_func(_fmt, ##__VA_ARGS__);
\
| ^~~~~~~~~~~
/usr/local/share/systemtap/runtime/linux/print.c:348:9: note: in expansion of
macro ‘printk’
348 | printk(KERN_DEBUG
| ^~~~~~
/usr/local/share/systemtap/runtime/linux/print.c:366:44: error: ‘struct module’
has no member named ‘core_size’
366 | (unsigned long) (THIS_MODULE->core_size -
THIS_MODULE->core_text_size)/1024,
| ^~
./include/linux/printk.h:427:33: note: in definition of macro
‘printk_index_wrap’
427 | _p_func(_fmt, ##__VA_ARGS__);
\
| ^~~~~~~~~~~
/usr/local/share/systemtap/runtime/linux/print.c:348:9: note: in expansion of
macro ‘printk’
348 | printk(KERN_DEBUG
| ^~~~~~
/usr/local/share/systemtap/runtime/linux/print.c:366:71: error: ‘struct module’
has no member named ‘core_text_size’; did you mean ‘kprobes_text_size’?
366 | (unsigned long) (THIS_MODULE->core_size -
THIS_MODULE->core_text_size)/1024,
|
^~~~~~~~~~~~~~
./include/linux/printk.h:427:33: note: in definition of macro
‘printk_index_wrap’
427 | _p_func(_fmt, ##__VA_ARGS__);
\
| ^~~~~~~~~~~
/usr/local/share/systemtap/runtime/linux/print.c:348:9: note: in expansion of
macro ‘printk’
348 | printk(KERN_DEBUG
| ^~~~~~
/usr/local/share/systemtap/runtime/linux/print.c:367:46: error: ‘struct module’
has no member named ‘core_text_size’; did you mean ‘kprobes_text_size’?
367 | (unsigned long) (THIS_MODULE->core_text_size)/1024,
| ^~~~~~~~~~~~~~
./include/linux/printk.h:427:33: note: in definition of macro
‘printk_index_wrap’
427 | _p_func(_fmt, ##__VA_ARGS__);
\
| ^~~~~~~~~~~
/usr/local/share/systemtap/runtime/linux/print.c:348:9: note: in expansion of
macro ‘printk’
348 | printk(KERN_DEBUG
| ^~~~~~
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.build:252:
/tmp/stapcVlKLM/stap_9691453a981c3fed6300ada89e578986_1302_src.o] Error 1
make: *** [Makefile:2043: /tmp/stapcVlKLM] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "stap_9691453a981c3fed6300ada89e578986_1302.ko" in
20970usr/4470sys/13543real ms.
Pass 4: compilation failed. [man error::pass4]
[root@rawh ~]#
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-05-03 8:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 8:56 mcermak at redhat dot com [this message]
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
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@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).