Messages in this thread | | | From | Vince Weaver <> | Date | Tue, 10 Apr 2018 10:48:19 -0400 (EDT) | Subject | perf: fuzzer leads to trace_kprobe: Could not insert message flood |
| |
Author: Song Liu <songliubraving@fb.com> Date: Wed Dec 6 14:45:15 2017 -0800
When running the perf_fuzzer on a current git checkout my logs are flooded with messages such as this: [71487.869077] trace_kprobe: Could not insert probe at unknown+0: -22 [71488.174479] trace_kprobe: Could not insert probe at unknown+0: -22
Presumably this is due to the introduction of the perf_kprobe PMU in commit e12f03d7031a977356e3d7b75a68c2185ff8d155 Author: Song Liu <songliubraving@fb.com> Date: Wed Dec 6 14:45:15 2017 -0800
Is there a way to get this error disabled, or else rate-limited?
Vince
| |