src/cddl/usr.sbin/dtrace, branch mainFreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=main2025-11-24T15:47:10ZUse ZFSTOP more broadly2025-11-24T15:47:10ZJohn Baldwinjhb@FreeBSD.org2025-11-24T15:47:10Zurn:sha1:e928afc531e68b7a142ee49d8f7e5c8426d54033
Reviewed by: brooks
Obtained from: CheriBSD
Differential Revision: https://reviews.freebsd.org/D53791
zfs: fix build after openzfs/zfs@e63d026b92025-11-17T16:11:56ZMartin Matuskamm@FreeBSD.org2025-11-16T11:15:14Zurn:sha1:4303bde4297a3d19cabdb08ce1550f682578d2ba
Fix Makefiles
Update zfs_config.h and zfs_gitrev.h
libdtrace: Permit taking the address of an identifier without type info2025-07-21T14:57:58ZMark Johnstonmarkj@FreeBSD.org2025-07-21T13:34:30Zurn:sha1:dabde7d97680cac7e0ead56693d424f4e5631019
Symbols defined using assembler directives lack type info, but in this
case one ought to be able to cast a pointer to the symbol and
dereference the pointer to get a value. Without this change, D
disallows this trick since it requires all identifiers to have a type.
Relax the rules slightly and allow an identifier to have type "void" if
we know we're just taking its address.
As a result, the following dtrace invocation works:
dtrace -n 'tick-1s {printf("%d", *(int *)&`ticks);}'
In particular, since commit b2b974f7ef4c ("clock: Simplify subr_ticks
and rename"), "ticks" does not have any type info associated with it, so
its value couldn't be printed. This trick provides a workaround and is
probably generally useful.
Add a regression test which exercises this functionality.
PR: 287752
Reviewed by: avg
MFC after: 1 month
Differential Revision: https://reviews.freebsd.org/D51417
dtrace tests: Fix the ATF config variable name2025-01-23T19:09:56ZMark Johnstonmarkj@FreeBSD.org2025-01-23T19:09:56Zurn:sha1:fed08c59b7bf2cb4d05bacadadde2dcef4dc6c46
Fixes: 6e6a67e98652 ("dtrace tests: Avoid hard-coding paths to required programs")
Sponsored by: Innovate UK
dtrace tests: Avoid hard-coding paths to required programs2025-01-22T14:20:33ZMark Johnstonmarkj@FreeBSD.org2025-01-22T14:20:33Zurn:sha1:6e6a67e98652e1477973d031b27ce085d7f200c2
MFC after: 1 week
Sponsored by: Innovate UK
dtrace tests: Add a test case which validates FBT probe arguments2024-09-19T09:22:03ZMark Johnstonmarkj@FreeBSD.org2024-09-19T09:22:03Zurn:sha1:d439598dd0d341b0c0b77151ba904e09c42f8421
Reviewed by: avg
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D46674
Remove residual blank line at start of Makefile2024-07-15T22:43:39ZWarner Loshimp@FreeBSD.org2024-07-15T04:46:32Zurn:sha1:e9ac41698b2f322d55ccf9da50a3596edb2c1800
This is a residual of the $FreeBSD$ removal.
MFC After: 3 days (though I'll just run the command on the branches)
Sponsored by: Netflix
dtrace tests: Regenerate makefiles after commit d0b2dbfa0ecf2024-06-01T15:16:39ZMark Johnstonmarkj@FreeBSD.org2024-06-01T15:16:39Zurn:sha1:397e83df75e0fcd0d3fcb95ae4d794cb7600fc89dtrace tests: Fix loading of the test kernel module2024-06-01T15:16:33ZMark Johnstonmarkj@FreeBSD.org2024-06-01T15:16:33Zurn:sha1:cb6b5e8ab9cfe3938855826fa3de0f58dacd364e
The old way is racy and can cause two instances, running in parallel, to
attempt to load dtrace_test, and only one will succeed. This caused
errors when running dtrace tests in parallel.
MFC after: 1 week
dtrace tests: Diff expected and actual output upon a miscompare2024-01-10T23:19:36ZMark Johnstonmarkj@FreeBSD.org2024-01-10T21:38:30Zurn:sha1:a61d2c7fbd3c87126db93dfe83b9f96fea3156f8
This makes quick diagnosis of test failures easier.
MFC after: 1 week