public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: eugene.loh@oracle.com
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: [PATCH] NEWS/dtrace.spec: Add items for release 2.0.5
Date: Wed,  4 Feb 2026 08:09:03 -0500	[thread overview]
Message-ID: <20260204130903.3426-1-eugene.loh@oracle.com> (raw)

From: Eugene Loh <eugene.loh@oracle.com>

Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
---
 NEWS        | 4 +++-
 dtrace.spec | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/NEWS b/NEWS
index 8f9ea6f4..bd20932a 100644
--- a/NEWS
+++ b/NEWS
@@ -1,4 +1,4 @@
-2.0.5-1 (Jan 27th, 2026)
+2.0.5-1 (Feb 4th, 2026)
 ------------------------
 
 New features:
@@ -9,6 +9,8 @@ Bugfixes:
 
  - Allocate the buffers BPF map to fit highest CPU id.
 
+ - Fix argument handling for multi-location user probes.
+
  - Change the "stack skip" to 3 for fbt (fprobe) and rawtp providers.
 
  - Fix prvname so that both rawfbt and fbt probes are seen.
diff --git a/dtrace.spec b/dtrace.spec
index d43b3c20..ee6c37b0 100644
--- a/dtrace.spec
+++ b/dtrace.spec
@@ -230,9 +230,11 @@ systemctl start dtprobed || :
 %{_libdir}/dtrace/testsuite
 
 %changelog
-* Tue Jan 27 2026 Eugene Loh <eugene.loh@oracle.com> - 2.0.5-1
+* Wed Feb  4 2026 Eugene Loh <eugene.loh@oracle.com> - 2.0.5-1
 - Implement PID-specific uprobes.  (Kris Van Hees)
 - Allocate the buffers BPF map to fit highest CPU id.  (Kris Van Hees)
+- Fix argument handling for multi-location user probes.
+  (Kris Van Hees) [Orabug: 38922360]
 - Change the "stack skip" to 3 for fbt (fprobe) and rawtp providers.
   [Orabug: 38776929]
 - Fix prvname so that both rawfbt and fbt probes are seen.
-- 
2.47.3


             reply	other threads:[~2026-02-04 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 13:09 eugene.loh [this message]
2026-02-04 15:29 ` [PATCH] NEWS/dtrace.spec: Add items for release 2.0.5 Kris Van Hees

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=20260204130903.3426-1-eugene.loh@oracle.com \
    --to=eugene.loh@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.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