Revision 7fa598f9706d40bd16f2ab286bdf5808e1393d35 authored by Steven Rostedt (VMware) on 27 October 2021, 16:08:54 UTC, committed by Steven Rostedt (VMware) on 28 October 2021, 01:47:55 UTC
When the syscall trace points are not configured in, the kselftests for
ftrace will try to attach an event probe (eprobe) to one of the system
call trace points. This triggered a WARNING, because the failure only
expects to see memory issues. But this is not the only failure. The user
may attempt to attach to a non existent event, and the kernel must not
warn about it.
Link: https://lkml.kernel.org/r/20211027120854.0680aa0f@gandalf.local.home
Fixes: 7491e2c442781 ("tracing: Add a probe that attaches to trace events")
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
1 parent 4e84dc4
| File | Mode | Size |
|---|---|---|
| apparmor | ||
| bpf | ||
| integrity | ||
| keys | ||
| landlock | ||
| loadpin | ||
| lockdown | ||
| safesetid | ||
| selinux | ||
| smack | ||
| tomoyo | ||
| yama | ||
| Kconfig | -rw-r--r-- | 10.8 KB |
| Kconfig.hardening | -rw-r--r-- | 10.4 KB |
| Makefile | -rw-r--r-- | 892 bytes |
| commoncap.c | -rw-r--r-- | 42.8 KB |
| device_cgroup.c | -rw-r--r-- | 21.1 KB |
| inode.c | -rw-r--r-- | 10.6 KB |
| lsm_audit.c | -rw-r--r-- | 10.9 KB |
| min_addr.c | -rw-r--r-- | 1.3 KB |
| security.c | -rw-r--r-- | 65.7 KB |
Computing file changes ...
