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/30716] On x86_64 get objtool warnings:  call to __get_user_nocheck_1() with UACCESS enabled
Date: Tue, 05 Mar 2024 00:33:06 +0000	[thread overview]
Message-ID: <bug-30716-6586-qlbZ9OiMZp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30716-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30716

--- Comment #4 from William Cohen <wcohen at redhat dot com> ---
Created attachment 15385
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15385&action=edit
Linux kernel make file define to disable objtool

Looking through the kernel code I found that an entry in Makefiles to disable
objtool:

https://elixir.bootlin.com/linux/v6.8-rc7/source/scripts/Makefile.build#L212

I have tried the patch out on RHEL9 which is most affected and the patch
eliminates the warnings.  Also tried on RHEL8 to verify that instrumentation
still compiled.  Now making a more extensive "make installcheck" on RHEL8/9,
fedora39, and rawhide.

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

  parent reply	other threads:[~2024-03-05  0:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 15:28 [Bug runtime/30716] New: " wcohen at redhat dot com
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 [this message]
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-qlbZ9OiMZp@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).