From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30617] Systemtap unable to successfully build kernel modules for linux-6.5
Date: Mon, 10 Jul 2023 15:08:38 +0000 [thread overview]
Message-ID: <bug-30617-6586-tWvV0HpFtO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30617-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30617
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
Following test provided reasonable results on Fedora rawhide and RHEL8:
sudo ../install/bin/stap --example para-callgraph.stp
'process("/usr/bin/ls").function("*")' -c /usr/bin/ls
The following also produced reasonable results on Fedora rawhide and RHEL8:
sudo ../install/bin/stap --example glibc-malloc.stp -c 'stap --dump-functions'
The patch is in the master branch as:
commit e891a37e366362a12ca311439918d69ffe641cec (HEAD -> master, origin/master,
origin/HEAD)
Author: William Cohen <wcohen@redhat.com>
Date: Sun Jul 9 16:46:20 2023 -0400
Adjust runtime _access_process_vm_ to work with linux 6.5
Linux kernel commit ca5e863233e8f6acd1792fd85d6bc2729a1b2c10
eliminated the vma argument for ‘get_user_pages_remote. For linux 6.5
kernel use the get_user_page_vma_remote function in its place like the
__access_remote_vm function in mm/memory.c of the kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-07-10 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:21 [Bug runtime/30617] New: Systemtap unable to successfully build kernel modules linux-6.5 wcohen at redhat dot com
2023-07-05 14:24 ` [Bug runtime/30617] Systemtap unable to successfully build kernel modules for linux-6.5 wcohen at redhat dot com
2023-07-06 16:05 ` wcohen at redhat dot com
2023-07-10 14:16 ` wcohen at redhat dot com
2023-07-10 15:08 ` wcohen at redhat dot com [this message]
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-30617-6586-tWvV0HpFtO@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).