Linux Trace Kernel
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Cc: linux-trace-kernel@vger.kernel.org,
	Gabriele Monaco <gmonaco@redhat.com>,
	unknownbbqrx <dev@unknownbbqr.xyz>, Wen Yang <wen.yang@linux.dev>
Subject: [GIT PULL] rv fixes for v7.1
Date: Wed,  3 Jun 2026 14:50:56 +0200	[thread overview]
Message-ID: <20260603125056.75559-1-gmonaco@redhat.com> (raw)

Steve,

The following changes since commit e43ffb69e0438cddd72aaa30898b4dc446f664f8:

  Linux 7.1-rc6 (2026-05-31 15:14:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gmonaco/linux.git rv-fixes-7.1

for you to fetch changes up to 44c2e91a684132ff0e47dc1f792bbdb42d64bd64:

  verification/rvgen: Fix ltl2k writing True as a literal (2026-06-03 13:20:58 +0200)

----------------------------------------------------------------
rv fixes for v7.1

Summary of changes:

- Fix reset ordering on per-task destruction

  Reset the task before dropping the slot instead of after, which was
  causing out-of-bound memory accesses.

- Fix HA monitor synchronization and cleanup

  Ensure synchronous cleanup for HA monitors by running timer callbacks
  in RCU read-side critical sections and using synchronize_rcu() during
  destruction.

- Avoid armed timers after tasks exit

  Add automatic cleanup for per-task HA monitors to prevent timers from
  firing after task exit.

- Fix memory ordering for DA/HA monitors

  Fix race conditions during monitor start by using release-acquire
  semantics for the monitoring flag.

- Fix initialization for DA/HA monitors

  Ensure monitors are not initialized relying on potentially corrupted
  state like the monitoring flag, that is not reset by all monitors type
  and may have an unknown state in monitors reusing the storage
  (per-task).

- Fix memory safety in per-task and per-object monitors

  Prevent use-after-free and out-of-bounds access by synchronizing with
  in-flight tracepoint probes using tracepoint_synchronize_unregister()
  before freeing monitor storage or releasing task slots.

- Adjust monitors for preemptible tracepoints

  Fix monitors that relied on tracepoints disabling preemption.
  Explicitly disable task migration when per-CPU monitors handle events
  to avoid accessing the wrong state and update the opid monitor logic.

- Fix incorrect __user specifier usage

  Remove __user from a non-pointer variable in the extract_params()
  helper.

- Fix bugs in the rv tool

  Ensure strings are NUL-terminated, fix substring matching in monitor
  searches, and improve cleanup and exit status handling.

- Fix several bugs in rvgen

  Fix LTL literal stringification, subparsers' options handling, and
  suffix stripping in dot2k.

----------------------------------------------------------------
Gabriele Monaco (15):
      rv: Fix __user specifier usage in extract_params()
      rv: Reset per-task DA monitors before releasing the slot
      rv: Prevent in-flight per-task handlers from using invalid slots
      rv: Ensure all pending probes terminate on per-obj monitor destroy
      rv: Do not rely on clean monitor when initialising HA
      rv: Add automatic cleanup handlers for per-task HA monitors
      rv: Ensure synchronous cleanup for HA monitors
      rv: Prevent task migration while handling per-CPU events
      rv: Use 0 to check preemption enabled in opid
      tools/rv: Fix substring match bug in monitor name search
      tools/rv: Fix substring match when listing container monitors
      tools/rv: Fix cleanup after failed trace setup
      verification/rvgen: Fix suffix strip in dot2k
      verification/rvgen: Fix options shared among commands
      verification/rvgen: Fix ltl2k writing True as a literal

Wen Yang (1):
      rv: Fix monitor start ordering and memory ordering for monitoring flag

unknownbbqrx (1):
      tools/rv: Ensure monitor name and desc are NUL-terminated

 include/rv/da_monitor.h                            | 139 +++++++++++++++++----
 include/rv/ha_monitor.h                            |  91 +++++++++++++-
 include/rv/ltl_monitor.h                           |   1 +
 kernel/trace/rv/monitors/deadline/deadline.h       |   3 +-
 kernel/trace/rv/monitors/nomiss/nomiss.c           |   4 +-
 kernel/trace/rv/monitors/opid/opid.c               |  12 +-
 kernel/trace/rv/monitors/stall/stall.c             |   4 +-
 tools/verification/rv/src/in_kernel.c              |  65 +++++-----
 tools/verification/rvgen/__main__.py               |  10 +-
 tools/verification/rvgen/rvgen/dot2k.py            |   4 +-
 tools/verification/rvgen/rvgen/ltl2ba.py           |   9 +-
 .../rvgen/rvgen/templates/dot2k/main.c             |   4 +-
 12 files changed, 263 insertions(+), 83 deletions(-)

To: Steven Rostedt <rostedt@goodmis.org>
Cc: Gabriele Monaco <gmonaco@redhat.com>
Cc: unknownbbqrx <dev@unknownbbqr.xyz>
Cc: Wen Yang <wen.yang@linux.dev>


             reply	other threads:[~2026-06-03 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 12:50 Gabriele Monaco [this message]
2026-06-03 23:16 ` [GIT PULL] rv fixes for v7.1 Steven Rostedt

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=20260603125056.75559-1-gmonaco@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=dev@unknownbbqr.xyz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=wen.yang@linux.dev \
    /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