Thread (32 messages) 32 messages, 6 authors, 2022-01-12

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

From: Michael Schmitz <schmitzmic@gmail.com>
Date: 2022-01-12 07:54:54
Also in: linux-arch, linux-m68k, lkml

Possibly related (same subject, not in this thread)

Hi Finn,

Am 12.01.2022 um 16:32 schrieb Finn Thain:
On Wed, 12 Jan 2022, Michael Schmitz wrote:
quoted
I seem to recall we also tested those on your 040 and there was no
regression there, but I may be misremembering that.
I abandoned that regression testing exercise when unpatched mainline
kernels began failing on that machine. I'm in the process of setting up a
different 68040 machine.
Thanks for refreshing my memory!

Splitting my first patch as suggested by Al in order to defer handling 
of the syscall_trace_enter() return code would achieve what Geert 
suggested (eliminate m68k syscall_trace() altogether) without risk of 
regression. This would need to replace Eric's patch 8.

Do you want me to send such a version based on my old patch series, or 
would you rather prepare that yourself, Eric?

Cheers,

	Michael

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help