From: Ian Munsie <imun...@au1.ibm.com>
Since the ftrace event initialisation routine now verifies that either
the syscall number or the compat syscall number is valid and will not
create events for unmapped syscalls, it is unnecessary to explicitly
search for them, so remove it.
Signed-off-by: Ian Munsie <imun...@au1.ibm.com>
---
kernel/trace/trace_syscalls.c | 20 --------------------
1 files changed, 0 insertions(+), 20 deletions(-)
diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c
index c0041e3..108c2eb 100644
--- a/kernel/trace/trace_syscalls.c
+++ b/kernel/trace/trace_syscalls.c
@@ -528,26 +528,6 @@ int __init init_ftrace_syscalls(void)
meta->compat_syscall_nr = i;
compat_syscalls_metadata[i] = meta;
}
- /* now check if any compat_syscalls are not referenced */
- for (ftrace_event = __start_ftrace_events;
- (unsigned long)ftrace_event <
- (unsigned long)__stop_ftrace_events; ftrace_event++) {
-
- match = 0;
- if (!ftrace_event->name)
- continue;
- if (strcmp(ftrace_event->class->system,
"compat_syscalls"))
- continue;
- for (i = 0; i < NR_syscalls_compat; i++) {
- if (ftrace_event->data ==
- compat_syscalls_metadata[i]) {
- match = 1;
- break;
- }
- }
- if (!match)
- ftrace_event->name = NULL;
- }
}
#endif
return 0;
--
1.7.1
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
