Re: [PATCH 08/17] ptrace/m68k: Stop open coding ptrace_report_syscall

Hi Geert,

Am 12.01.2022 um 20:55 schrieb Geert Uytterhoeven:

Hi Michael,

quoted

What's the other reason these patches are still stuck, Geert? Did we
ever settle the dispute about what return code ought to abort a syscall
(in the seccomp context)?

IIRC, some (self)tests were still failing?

Too true - but I don't think my way of building the testsuite was entirely according to the book. And I'm not sure I ran the testsuite with more than one of the return code options. In all honesty, I had been waiting for Adrian Glaubitz to test the patches with his seccomp library port instead of relying on the testsuite.

Still, reason enough to split off the removal of syscall_trace() from the seccomp stuff if it helps with Eric's patch series.

Cheers,

	Michael

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds