Skip to contentSkip to conversation

selftests/ftrace: Fix BAD_TP_NAME marker in fprobe_syntax_errors

PATCH New Cao Ruichuang 1 participant 1 message Apr 7

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 selftests/ftrace: Fix BAD_TP_NAME marker in fprobe_syntax_errors

The BAD_TP_NAME check currently expects the error marker for t kmem/kfree to point at the slash. Current kernels report this parse error at the start of the invalid tracepoint name, so the selftest fails even though the input is still rejected.

Move the caret to match the reported error position.

---
 .../selftests/ftrace/test.d/dynevent/fprobe_syntax_errors.tc    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/ftrace/test.d/dynevent/fprobe_syntax_errors.tc +1 -1
index fee479295..e51f642c3 100644
@@ -27,7 +27,7 @@ check_error 'f:^foo.1/bar vfs_read'	# BAD_GROUP_NAME
 check_error 'f:^ vfs_read'		# NO_EVENT_NAME
 check_error 'f:foo/^12345678901234567890123456789012345678901234567890123456789012345 vfs_read'	# EVENT_TOO_LONG
 check_error 'f:foo/^bar.1 vfs_read'	# BAD_EVENT_NAME
-check_error 't kmem^/kfree'       # BAD_TP_NAME
+check_error 't ^kmem/kfree'       # BAD_TP_NAME
 
 check_error 'f vfs_read ^$stack10000'	# BAD_STACK_NUM
 
Signature · 1 line
2.39.5 (Apple Git-154)