On 01/14, Andrii Nakryiko wrote: > > On Tue, Jan 14, 2025 at 12:40 PM Oleg Nesterov <oleg@xxxxxxxxxx> wrote: > > > > But, unlike sys_uretprobe(), sys_rt_sigreturn() is old, so the existing > > setups must know that sigreturn() should be respected... > > someday sys_uretprobe will be old as well ;) FWIW, systemd allowlisted > sys_uretprobe, see [0] And I agree! ;) I mean, I'd personally prefer to do nothing and wait until userspace figures out that we have another "special" syscall. But can we do it? I simply do not know. Can we ignore this (valid) bug report? Oleg.
