From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/20282] New: implicit declaration of function ‘__get_user_bad’ on recent aarch64 kernel
Date: Tue, 21 Jun 2016 10:02:00 -0000 [thread overview]
Message-ID: <bug-20282-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=20282
Bug ID: 20282
Summary: implicit declaration of function ‘__get_user_bad’ on
recent aarch64 kernel
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: ---
With kernel-4.5.0-0.40.el7.aarch64 kbuild fails thusly:
=======
Pass 3: translated to C into
"/tmp/stapCJl99c/stap_355af5cf9305976cecf5dce2a13ff16c_53860_src.c" using
191104virt/82880res/6208shr/76096data kb, in 20usr/150sys/178real ms.
In file included from /usr/local/share/systemtap/runtime/linux/runtime.h:214:0,
from /usr/local/share/systemtap/runtime/runtime.h:26,
from
/tmp/stapCJl99c/stap_355af5cf9305976cecf5dce2a13ff16c_53860_src.c:25:
/usr/local/share/systemtap/runtime/stp_string.c: In function
‘_stp_decode_utf8’:
/usr/local/share/systemtap/runtime/stp_string.c:73:2: error: implicit
declaration of function ‘__get_user_bad’
[-Werror=implicit-function-declaration]
if (_stp_deref_nofault(b, 1, buf, (user ? USER_DS : KERNEL_DS)))
^
cc1: all warnings being treated as errors
=======
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2016-06-21 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 10:02 mcermak at redhat dot com [this message]
2016-06-21 18:18 ` [Bug runtime/20282] " dsmith 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-20282-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).