[DTrace-devel] [oracle/dtrace-utils] 02f327: dtprobed: handle a crashed parser child better

[Nick Alcock]

  Branch: refs/heads/devel
  Home:   https://github.com/oracle/dtrace-utils
  Commit: 02f327408812a4caa04db0096894471f98e6834e
      https://github.com/oracle/dtrace-utils/commit/02f327408812a4caa04db0096894471f98e6834e
  Author: Nick Alcock <nick.alcock at oracle.com>
  Date:   2025-01-16 (Thu, 16 Jan 2025)

  Changed paths:
    M dtprobed/dtprobed.c

  Log Message:
  -----------
  dtprobed: handle a crashed parser child better

When a parser child crashes and is restarted, its file handles
might change: we should pick up the new fhes if so.

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


  Commit: 68f2dec61aff39a775a2d7bed9904151aeb3e49b
      https://github.com/oracle/dtrace-utils/commit/68f2dec61aff39a775a2d7bed9904151aeb3e49b
  Author: Nick Alcock <nick.alcock at oracle.com>
  Date:   2025-01-17 (Fri, 17 Jan 2025)

  Changed paths:
    M libcommon/Build

  Log Message:
  -----------
  libcommon: turn off FORTIFY_SOURCE more aggressively

This is incompatible with dof_parser_t's use of trailing strings of
variable length, and buys us nothing anyway since we're running in a
seccomped parser child and any buffer overruns are harmless and cannot
result in anything other than a dying child.  We were already -U'ing
FORTIFY_SOURCE in libcommon_CPPFLAGS, but that precedes CFLAGS on the
command line, so if the build system passes -D_FORTIFY_SOURCE there, it
still takes effect.

Use _NOCFLAGS and _NOCPPFLAGS to explicitly disable every level of
fortification that currently exists.

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


  Commit: bb8fa79cbeda978da3123b9d4ad3afa570018924
      https://github.com/oracle/dtrace-utils/commit/bb8fa79cbeda978da3123b9d4ad3afa570018924
  Author: Nick Alcock <nick.alcock at oracle.com>
  Date:   2025-01-17 (Fri, 17 Jan 2025)

  Changed paths:
    M runtest.sh

  Log Message:
  -----------
  tests: do not pass -flto to the compiler or linker

We don't want to compile tests with -flto by default: if the distro
compiler automatically activates it, turn it off by explicitly passing
-fno-lto to all compiler and linker invocations in the testsuite.

(This is a bit fiddly because this is the first CPPFLAG which is
not also a valid flag to dtrace(1) itself, so we have to split
a variable up a bit.)

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


  Commit: 0fd90283cc03c640de3695d5f276dd6289a022db
      https://github.com/oracle/dtrace-utils/commit/0fd90283cc03c640de3695d5f276dd6289a022db
  Author: Nick Alcock <nick.alcock at oracle.com>
  Date:   2025-01-17 (Fri, 17 Jan 2025)

  Changed paths:
    M libdtrace/Build

  Log Message:
  -----------
  drti: do not compile with LTO

drti.o is shipped as object code and can be reused by many compiler
versions: we must not put LTO IR into it.

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


Compare: https://github.com/oracle/dtrace-utils/compare/a0a24ebf2a41...0fd90283cc03

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