[DTrace-devel] [oracle/dtrace-utils] d4c34e: btf: fix symbol BTF ID lookup

[Alan Maguire]

  Branch: refs/heads/devel
  Home:   https://github.com/oracle/dtrace-utils
  Commit: d4c34e9a3199f7509293a5c20b975f379baa3b84
      https://github.com/oracle/dtrace-utils/commit/d4c34e9a3199f7509293a5c20b975f379baa3b84
  Author: Kris Van Hees <kris.van.hees at oracle.com>
  Date:   2025-07-28 (Mon, 28 Jul 2025)

  Changed paths:
    M libdtrace/dt_bpf.c
    M libdtrace/dt_btf.c
    M libdtrace/dt_btf.h
    M libdtrace/dt_prov_fbt.c

  Log Message:
  -----------
  btf: fix symbol BTF ID lookup

The logic to perform a BTF ID lookup for a symbol did not guard against
BTF data not having been loaded for the module that contains the symbol.

Signed-off-by: Kris Van Hees <kris.van.hees at oracle.com>
Reviewed-by: Nick Alcock <nick.alcock at oracle.com>


  Commit: 1ceca59160ba1ab3a28d4f93abf6a36fea5a6854
      https://github.com/oracle/dtrace-utils/commit/1ceca59160ba1ab3a28d4f93abf6a36fea5a6854
  Author: Kris Van Hees <kris.van.hees at oracle.com>
  Date:   2025-07-28 (Mon, 28 Jul 2025)

  Changed paths:
    M libdtrace/dt_bpf.c
    M libdtrace/dt_prov_uprobe.c

  Log Message:
  -----------
  Free the DIFO for a probe once it is loaded

When a lot of probes are being probed, keeping all DIFO around consumes
a lot of memory.  Once the BPF program is loaded, the DIFO can be freed.

Signed-off-by: Kris Van Hees <kris.van.hees at oracle.com>
Reviewed-by: Eugene Loh <eugene.loh at oracle.com>


  Commit: 6642cf0c84de770b93a235581183a644664513a5
      https://github.com/oracle/dtrace-utils/commit/6642cf0c84de770b93a235581183a644664513a5
  Author: Alan Maguire <alan.maguire at oracle.com>
  Date:   2025-07-28 (Mon, 28 Jul 2025)

  Changed paths:
    M runtest.sh
    R test/unittest/ip/get.ipv4remote.pl
    R test/unittest/ip/get.ipv6remote.pl
    M test/unittest/ip/tst.ipv4remoteicmp.sh
    M test/unittest/ip/tst.ipv4remotetcp.sh
    M test/unittest/ip/tst.ipv4remoteudp.sh
    M test/unittest/ip/tst.ipv6remoteicmp.sh
    M test/unittest/tcp/tst.ipv4remotetcp.sh
    M test/unittest/tcp/tst.ipv4remotetcpstate.sh
    M test/unittest/udp/tst.ipv4remoteudp.sh
    A test/utils/get_remote.sh

  Log Message:
  -----------
  test/utils: add more reliable "get remote address" approach

The current approach of looking for remote addresses
is brittle and fails in many environments; it checks the
default route gateway and looks for open ports in the TCP
case.

We can however achieve the same goal reliably by creating
a network namespace on the system and configuring either
IPv4 or IPv6 addresses on the namespaced and local veth
interfaces that support communication between namespaces.
If a tcp port is required, start sshd to listen on that port.

Teardown of network namespaces is managed in the toplevel runtest.sh to
ensure that network namespaces are removed after test completion for all
cases: success, failure and timeout.

Move the get_remote.sh script to test/utils also as it
seems a more natural location.

One issue - this cannot be run on a local system with
a VPN running as the VPN connection is pretty aggressive
in disconnecting/reconnecting when spotting a link-up event
associated with the global netns side of the veth.  However
in my experience the remote IP tests do not work reliably
in that environment anyway.

Signed-off-by: Alan Maguire <alan.maguire at oracle.com>
Reviewed-by: Eugene Loh <eugene.loh at oracle.com>
Reviewed-by: Kris Van Hees <kris.van.hees at oracle.com>


Compare: https://github.com/oracle/dtrace-utils/compare/e3eecff2be8d...6642cf0c84de

To unsubscribe from these emails, change your notification settings at https://github.com/oracle/dtrace-utils/settings/notifications