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/30831] Systemtap scripts fail to compile on newest  linux 6.6 kernels
Date: Wed, 27 Sep 2023 14:24:22 +0000	[thread overview]
Message-ID: <bug-30831-6586-bELa4Ifq4b@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30831-6586@http.sourceware.org/bugzilla/>

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

--- Comment #5 from William Cohen <wcohen at redhat dot com> ---
Created attachment 15140
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15140&action=edit
eliminate problem use of flush_scheduled_work()

This patch allows systemtap to build modules for linux-6.6 kernels.  It has
been tested out on (running the examples tests):
  x86_64 fedora rawhide kernel-6.6.0-0.rc3.26.fc40.x86_64
  x86_64 f38 kernel-6.4.15-200.fc38.x86_64
  x86_64 rhel9 kernel-5.14.0-368.el9.x86_64
  x86_64 rhel8 kernel-4.18.0-514.el8.x86_64

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

  parent reply	other threads:[~2023-09-27 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 17:46 [Bug runtime/30831] New: The do_each_thread macro has been removed from " wcohen at redhat dot com
2023-09-07 19:23 ` [Bug runtime/30831] Systemtap scripts fail to compile on " wcohen at redhat dot com
2023-09-08  2:49 ` wcohen at redhat dot com
2023-09-18 13:46 ` wcohen at redhat dot com
2023-09-18 13:51 ` wcohen at redhat dot com
2023-09-27 14:24 ` wcohen at redhat dot com [this message]
2023-09-27 20:03 ` wcohen at redhat dot com
2023-11-23 15:16   ` Tetsuo Handa
2023-12-13 14:47     ` William Cohen
2023-12-17 10:41       ` Tetsuo Handa

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-30831-6586-bELa4Ifq4b@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).