summaryrefslogtreecommitdiff
path: root/rust/kernel/alloc
diff options
context:
space:
mode:
authorBrian Norris <briannorris@chromium.org>2026-11-16 18:27:11 -0800
committerSteven Rostedt <rostedt@goodmis.org>2026-11-20 10:02:38 -0500
commita152600010847fec3829c9302e6bab0e2b8d53b2 (patch)
tree624560376827db003b7f95862864725dc62d8b47 /rust/kernel/alloc
parent4d0d961873409168e77c6bbc1453fcf8ade37788 (diff)
tracing: Add tests for globbing number-based strings
In "tracing: Properly match strings that start with numbers", we fixed bugs related to string fields that start with a number and also use globs instead of full matches. Add some additional startup test cases for this. For easy reproducible testing, I abused the kunit.py script to boot a minimal kernel with FTRACE_STARTUP_TEST enabled: ./tools/testing/kunit/kunit.py run --arch=x86_64 \ --kconfig_add=CONFIG_FTRACE=y \ --kconfig_add=CONFIG_FUNCTION_TRACER=y \ --kconfig_add=CONFIG_DYNAMIC_FTRACE=y \ --kconfig_add=CONFIG_FTRACE_STARTUP_TEST=y \ --kconfig_add=CONFIG_EVENT_TRACE_STARTUP_TEST=n \ --raw_output=all deadbeef Relevant line: Testing ftrace filter: OK Without "tracing: Properly match strings that start with numbers", the test fails with: Testing ftrace filter: Failed to match filter 'str ~ "0001:*"', expected 1 Link: https://patch.msgid.link/20261116182710.2.Ic117871c2b1e94c5a2176903a5c3316a10584e61@changeid Signed-off-by: Brian Norris <briannorris@chromium.org> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'rust/kernel/alloc')
0 files changed, 0 insertions, 0 deletions