Skip to content

Commit a089bb2

Browse files
mhiramatshuahkh
authored andcommitted
selftests: tracing: Use mutex_unlock for testing glob filter
Since commit c5b6aba ("locking/mutex: implement mutex_trylock_nested") makes mutex_trylock() as an inlined function if CONFIG_DEBUG_LOCK_ALLOC=y, we can not use mutex_trylock() for testing the glob filter of ftrace. Use mutex_unlock instead. Link: https://lore.kernel.org/r/175151680309.2149615.9795104805153538717.stgit@mhiramat.tok.corp.google.com Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
1 parent 95d32c7 commit a089bb2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

tools/testing/selftests/ftrace/test.d/ftrace/func-filter-glob.tc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ ftrace_filter_check 'schedule*' '^schedule.*$'
2929
ftrace_filter_check '*pin*lock' '.*pin.*lock$'
3030

3131
# filter by start*mid*
32-
ftrace_filter_check 'mutex*try*' '^mutex.*try.*'
32+
ftrace_filter_check 'mutex*unl*' '^mutex.*unl.*'
3333

3434
# Advanced full-glob matching feature is recently supported.
3535
# Skip the tests if we are sure the kernel does not support it.

0 commit comments

Comments
 (0)