On Mon, Mar 18, 2019 at 10:49:21AM +0000, Sudeep Holla wrote: > Currently each architecture handles PTRACE_SYSEMU in very similar way. > It's completely arch independent and can be handled in the code helping > to consolidate PTRACE_SYSEMU handling. > > Let's introduce a hook 'ptrace_syscall_enter' that arch specific syscall > entry code can call.
Sorry if I'm late for the party, but the new name looks confusing. If all it does is related to TIF_SYSCALL_EMU, why does it have a generic name 'ptrace_syscall_enter' without any hint of being specific to TIF_SYSCALL_EMU? -- ldv
signature.asc
Description: PGP signature
