From: "zhangwei(Jovi)" <jovi.zhang...@huawei.com> ppc64 has its own syscall prefix like ".SyS" or ".sys". Make the comment in arch_syscall_match_sym_name() more understandable.
Link: http://lkml.kernel.org/r/513d842f.40...@huawei.com Signed-off-by: zhangwei(Jovi) <jovi.zhang...@huawei.com> Signed-off-by: Steven Rostedt <rost...@goodmis.org> --- kernel/trace/trace_syscalls.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c index 68f3f34..8f2ac73 100644 --- a/kernel/trace/trace_syscalls.c +++ b/kernel/trace/trace_syscalls.c @@ -37,7 +37,7 @@ static inline bool arch_syscall_match_sym_name(const char *sym, const char *name /* * Only compare after the "sys" prefix. Archs that use * syscall wrappers may have syscalls symbols aliases prefixed - * with "SyS" instead of "sys", leading to an unwanted + * with ".SyS" or ".sys" instead of "sys", leading to an unwanted * mismatch. */ return !strcmp(sym + 3, name + 3); -- 1.7.10.4
signature.asc
Description: This is a digitally signed message part
