From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22551] New: on rawhide, we're getting a compile error that init_timer() doesn't exist
Date: Tue, 05 Dec 2017 22:31:00 -0000 [thread overview]
Message-ID: <bug-22551-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=22551
Bug ID: 22551
Summary: on rawhide, we're getting a compile error that
init_timer() doesn't exist
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Target Milestone: ---
On 4.15.0-0.rc1.git3.1.fc28.x86_64, I'm seeing the following:
====
stap -p4 -e 'probe begin { exit() }'
In file included from
/usr/local/share/systemtap/runtime/transport/transport.c:65:0,
from /usr/local/share/systemtap/runtime/linux/print.c:17,
from /usr/local/share/systemtap/runtime/print.c:17,
from /usr/local/share/systemtap/runtime/runtime_context.h:22,
from
/tmp/stapn0pvvU/stap_a64b174160f580702e3079239f11b6ac_1080_src.c:53:
/usr/local/share/systemtap/runtime/transport/relay_v2.c: In function
‘__stp_relay_timer_init’:
/usr/local/share/systemtap/runtime/transport/relay_v2.c:154:2: error: implicit
declaration of function ‘init_timer’; did you mean ‘init_timers’?
[-Werror=implicit-function-declaration]
init_timer(&_stp_relay_data.timer);
^~~~~~~~~~
init_timers
/usr/local/share/systemtap/runtime/transport/relay_v2.c:156:33: error:
assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
_stp_relay_data.timer.function = __stp_relay_wakeup_timer;
^
/usr/local/share/systemtap/runtime/transport/relay_v2.c:157:23: error: ‘struct
timer_list’ has no member named ‘data’
_stp_relay_data.timer.data = 0;
^
In file included from /usr/local/share/systemtap/runtime/linux/print.c:17:0,
from /usr/local/share/systemtap/runtime/print.c:17,
from /usr/local/share/systemtap/runtime/runtime_context.h:22,
from
/tmp/stapn0pvvU/stap_a64b174160f580702e3079239f11b6ac_1080_src.c:53:
/usr/local/share/systemtap/runtime/transport/transport.c: In function
‘_stp_attach’:
/usr/local/share/systemtap/runtime/transport/transport.c:328:31: error:
assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
_stp_ctl_work_timer.function = _stp_ctl_work_callback;
^
/usr/local/share/systemtap/runtime/transport/transport.c:329:21: error: ‘struct
timer_list’ has no member named ‘data’
_stp_ctl_work_timer.data= 0;
^
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.build:310:
/tmp/stapn0pvvU/stap_a64b174160f580702e3079239f11b6ac_1080_src.o] Error 1
make: *** [Makefile:1506: _module_/tmp/stapn0pvvU] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed. [man error::pass4]
====
The first error, "implicit declaration of function ‘init_timer’" seems to be
caused by the following upstream kernel commit:
====
commit 7eeb6b893bd28c68b6d664de1d3120e49b855cdb
Author: Kees Cook <keescook@chromium.org>
Date: Wed Oct 11 23:13:49 2017 -0700
timer: Remove init_timer() interface
All users of init_timer() have been updated. Remove the ancient interface.
====
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2017-12-05 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 22:31 dsmith at redhat dot com [this message]
2017-12-06 20:38 ` [Bug runtime/22551] " dsmith at redhat dot com
2017-12-07 4:47 ` lufq.fnst at cn dot fujitsu.com
2017-12-07 10:44 ` fche at redhat dot com
2017-12-07 12:00 ` lufq.fnst at cn dot fujitsu.com
2017-12-07 16:01 ` dsmith at redhat dot com
2017-12-08 1:32 ` lufq.fnst at cn dot fujitsu.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-22551-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).