[Bug runtime/33324] New: runtime/transport/relay_v2.c incompatible with Kernel-6.17

[mcermak at redhat dot com]

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

            Bug ID: 33324
           Summary: runtime/transport/relay_v2.c incompatible with
                    Kernel-6.17
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com
  Target Milestone: ---

Created attachment 16286
  --> https://sourceware.org/bugzilla/attachment.cgi?id=16286&action=edit
Tweak making stap work with kernel-6.17

Seems like systemtap runtime needs to reflect the following linux commit:

$ git log -S prev_padding
commit 2489e958129ff7cbf26a34ee33cdc9ccbd68fe3c
Author: Jason Xing <kernelxing@tencent.com>
Date:   Thu Jun 12 14:11:57 2025 +0800

    relayfs: abolish prev_padding

    Patch series "relayfs: misc changes", v5.

    The series mostly focuses on the error counters which helps every user
    debug their own kernel module.


    This patch (of 5):

    prev_padding represents the unused space of certain subbuffer.  If the
    content of a call of relay_write() exceeds the limit of the remainder of
    this subbuffer, it will skip storing in the rest space and record the
    start point as buf->prev_padding in relay_switch_subbuf().  Since the buf
    is a per-cpu big buffer, the point of prev_padding as a global value for
    the whole buffer instead of a single subbuffer (whose padding info is
    stored in buf->padding[]) seems meaningless from the real use cases, so we
    don't bother to record it any more.


The attached quick patch seems to help on my test system (but breaks the
backwards compatibility, so needs more work)

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