From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31039] implicit declaration of function ‘stap_task_finder_complete’
Date: Mon, 11 Dec 2023 22:15:26 +0000 [thread overview]
Message-ID: <bug-31039-6586-DocaV3tGa8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31039-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31039
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
This has been fixed by:
commit 39b3819b69536e8a652920bf491442f26e187a19 (HEAD -> master, origin/master,
origin/HEAD)
Author: William Cohen <wcohen@redhat.com>
Date: Mon Dec 11 17:03:18 2023 -0500
PR31039: Make autoconf-utrace-via-tracepoints.c work with struct folio
Newer linux kernels are using struct folio in place of struct page.
Kernel git commit 8c9ae56dc73b5ae48 replaces the struct page argument
in should_numa_migrate_memory() with a struct folio. To make the
autoconf-utrace-via-tracepoints.c test compile properly needed to add
an include to pull in the struct folio definition. This allows the
auto_path.exp and many other tests using userspace probes to function
properly on the newer Linux 6.7 kernels.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-12-11 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 14:39 [Bug runtime/31039] New: " mcermak at redhat dot com
2023-12-06 22:36 ` [Bug runtime/31039] " wcohen at redhat dot com
2023-12-11 21:08 ` wcohen at redhat dot com
2023-12-11 22:15 ` 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-31039-6586-DocaV3tGa8@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).