From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30716] New: On x86_64 get objtool warnings: call to __get_user_nocheck_1() with UACCESS enabled
Date: Wed, 02 Aug 2023 15:28:22 +0000 [thread overview]
Message-ID: <bug-30716-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30716
Bug ID: 30716
Summary: On x86_64 get objtool warnings: call to
__get_user_nocheck_1() with UACCESS enabled
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
With linux 6.x kernels the current git checkout of systemtap gets warnings like
the following on x86_64 machines:
../install/bin/stap --example -p4 stap_time.stp
/tmp/stapaDfnF3/stap_d27d31c04f7b6439f67d919b5ec15337_6499.o: warning: objtool:
probe_54014+0xd4f: call to __get_user_nocheck_1() with UACCESS enabled
/home/wcohen/.systemtap/cache/d2/stap_d27d31c04f7b6439f67d919b5ec15337_6499.ko
This is introduced by systemtap git commit a9337abbb213e8. If that particular
commit is removed the warning goes away.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-08-02 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 15:28 wcohen at redhat dot com [this message]
2023-08-03 19:45 ` [Bug runtime/30716] " wcohen at redhat dot com
2023-08-23 13:09 ` fche at redhat dot com
2023-10-25 23:09 ` wcohen at redhat dot com
2024-03-05 0:33 ` wcohen at redhat dot com
2024-03-07 18:55 ` wcohen 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-30716-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).