From: Kris Van Hees <noreply@github.com>
To: dtrace@lists.linux.dev
Subject: [oracle/dtrace] 1b367f: uprobe: fix memory leak
Date: Tue, 28 Apr 2026 14:36:11 -0700 [thread overview]
Message-ID: <oracle/dtrace/push/refs/heads/dev-queue/a00035-505124@github.com> (raw)
Branch: refs/heads/dev-queue
Home: https://github.com/oracle/dtrace
Commit: 1b367f0f0b601d5996a83d6be6c1f544f8b90f01
https://github.com/oracle/dtrace/commit/1b367f0f0b601d5996a83d6be6c1f544f8b90f01
Author: Kris Van Hees <kris.van.hees@oracle.com>
Date: 2026-04-28 (Tue, 28 Apr 2026)
Changed paths:
M libdtrace/dt_prov_uprobe.c
Log Message:
-----------
uprobe: fix memory leak
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Commit: e6025d2758eaeeba5e5f2ece3b702bd3e077a0a7
https://github.com/oracle/dtrace/commit/e6025d2758eaeeba5e5f2ece3b702bd3e077a0a7
Author: Kris Van Hees <kris.van.hees@oracle.com>
Date: 2026-04-28 (Tue, 28 Apr 2026)
Changed paths:
M libdtrace/dt_btf.c
M libdtrace/dt_btf.h
Log Message:
-----------
btf: btf argument to dt_btf_get_string() should be const
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Commit: 3988539235df2ed9364115704dfb6e40d021b310
https://github.com/oracle/dtrace/commit/3988539235df2ed9364115704dfb6e40d021b310
Author: Kris Van Hees <kris.van.hees@oracle.com>
Date: 2026-04-28 (Tue, 28 Apr 2026)
Changed paths:
M libdtrace/dt_btf.c
Log Message:
-----------
btf: use dt_btf_real_type_by_id() to resolve types
Functions that need to check type data operate on the real type rather
than a typedef or a type with modifiers. Similarly, when a type of a
function is needed, the prototype (BTF type BTF_KIND_PROTO) is what is
really needed.
Introducing dt_btf_real_type_by_id() removed duplication of code in other
functions.
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Commit: 76fef5fa3ad26cd49bfdf44ceb3340d7786b3de1
https://github.com/oracle/dtrace/commit/76fef5fa3ad26cd49bfdf44ceb3340d7786b3de1
Author: Kris Van Hees <kris.van.hees@oracle.com>
Date: 2026-04-28 (Tue, 28 Apr 2026)
Changed paths:
M libdtrace/dt_btf.c
M libdtrace/dt_btf.h
Log Message:
-----------
btf: add dt_btf_func_is_traceable()
Add a function to determine whether a function (given by BTF id) can be
traced using BPF fentry/fexit probes. It implements checks inspired by
btf_distill_func_proto() in kernel/bpf/btf.c.
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Commit: 3cb31b76656452927ada5b1e1d135887e78857ac
https://github.com/oracle/dtrace/commit/3cb31b76656452927ada5b1e1d135887e78857ac
Author: Kris Van Hees <kris.van.hees@oracle.com>
Date: 2026-04-28 (Tue, 28 Apr 2026)
Changed paths:
M libdtrace/dt_prov_fbt.c
Log Message:
-----------
fbt: do not provide untraceable functions (for fprobes)
Ensure that we do not provide FBT probes for functions that cannot be
probed using BPF fentry/fexit probes if fprobes are the default.
The provide_probe() function now takes a dt_module_t argument so that
dt_btf_func_is_traceable() can be called.
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Commit: 5051249e1bd0553d17eacd1ae486775a62c51ebd
https://github.com/oracle/dtrace/commit/5051249e1bd0553d17eacd1ae486775a62c51ebd
Author: Kris Van Hees <kris.van.hees@oracle.com>
Date: 2026-04-28 (Tue, 28 Apr 2026)
Changed paths:
M libdtrace/dt_prov_fbt.c
A test/unittest/codegen/tst.fbt-return.d
A test/unittest/codegen/tst.fbt-return.r
Log Message:
-----------
fbt: retrieve function return value using helper
We were causing BPF verifier errors when trying to access the return value
of some functions due to incorrect calculation of the offset to read from.
Rather than implementing the more complex logic needed to calculate the
proper offset of the return value, we can just use the bpf_get_func_ret()
BPF helper. This does not impose a performance decrease because that
helper gets inlined by the BPF verifier.
Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
Compare: https://github.com/oracle/dtrace/compare/a000357c8746...5051249e1bd0
To unsubscribe from these emails, change your notification settings at https://github.com/oracle/dtrace/settings/notifications
reply other threads:[~2026-04-28 21:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=oracle/dtrace/push/refs/heads/dev-queue/a00035-505124@github.com \
--to=noreply@github.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