On Fri, Feb 21, 2020 at 5:50 AM Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > Use of memmove() in #DF is problematic when you consider tracing and > other instrumentation. > > Remove the memmove() call and simply write out what need doing; Boris > argues the ranges should not overlap. > > Survives selftests/x86, specifically sigreturn_64. > > (Andy ?!) Acked-by: Andy Lutomirski <luto@xxxxxxxxxx> Even ignoring the tracing issue, I think this is nicer than the original code.