public inbox for
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <>
Subject: [Bug runtime/30831] Systemtap scripts fail to compile on newest  linux 6.6 kernels
Date: Wed, 27 Sep 2023 20:03:18 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from William Cohen <wcohen at redhat dot com> ---
The following commit have been added to the systemtap master git repo to
address the issues with building systemtap instrumentation with the linux-6.6

commit ca71442b93af61cbd9a1386e24e967373f928eae (HEAD -> master, origin/master,
Author: William Cohen <>
Date:   Wed Sep 27 10:09:11 2023 -0400

    Eliminate use of kernel's flush_scheduled_work() in systemtap modules

    Kernel git commit 20bdedafd2f63e0ba70991127f9b5c0826ebdb32 turns use
    of flush_scheduled_work() into a warning which causes builds of
    anything using it to fail because warnings are treated as errors.
    Previous users of flush_scheduled_work() in the kernel have been
    converted over to use individual workqueues.  Systemtap runtime now
    does the same.  It creates and uses its own workqueue to eliminate the
    use of flush_scheduled_work().

commit 1ed860193216de3b233da440b2f9d52d94770b43
Author: William Cohen <>
Date:   Fri Sep 15 15:12:11 2023 -0400

    Use TWA_RESUME in the runtime calls to task_work_add

    Kernel git commit c40e60f00caf18bc382215c79651777eb40f5f9d in the
    linux 6.6 kernels will cause the implicit conversion of boolean true
    to an enum task_work_notify_mode to be flagged resulting in the
    systemtap instrumentation compile to fail.  Adding a config check to
    use TWA_RESUME if it is available or pass in the equivalent true
    argument for older kernels.

commit 21bb398cb78b4274577c8ef2483ea2d03beaf7f4
Author: William Cohen <>
Date:   Tue Sep 12 11:34:24 2023 -0400

    Eliminate use of do_each_thread() macro

    The Linux kernel commit 5ffd2c37cb7a5 removed the do_each_thread()
    macro and suggests using the for_each_process_thread() in its place.
    The Systemtap runtime has been migrated to using the more concise
    macro.  The for_each_process_thread() macro was added by commit
    0c740d0afc3bff to Linux 3.14, January 2014, almost a decade ago, so it
    should be available on modern systems.

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

  parent reply	other threads:[~2023-09-27 20:03 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
2023-09-27 20:03 ` wcohen at redhat dot com [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).