On 08/25, Oleg Nesterov wrote: > > At least I certainly disagree with "Fixes: c1ae5c75e103" ;) > > uretprobe_perf_func/etc was designed for perf, and afaics this code still > works fine even if you run 2 perf-record's with -p PID1/PID2 at the same > time. Forgot to mention... And note that in this case uprobe_perf_func()->uprobe_perf_filter() will never return false, and this is correct. Oleg.