On Mon, Aug 06, 2012 at 06:05:30PM +0200, Richard Weinberger wrote:
> Hmm, is it a good idea to call syscall_trace_leave() in any case?
> E.g. if syscall_trace_enter() fails for whatever reason...
I have replicated the behavior of other architectures.
For example in x86/32 a.k.a. i386:
arch/x86/ke
Am 06.08.2012 17:37, schrieb Renzo Davoli:
> ---
> diff -Naur linux-3.6-rc1/arch/um/include/asm/ptrace-generic.h
> linux-3.6-rc1.tracehook/arch/um/include/asm/ptrace-generic.h
> --- linux-3.6-rc1/arch/um/include/asm/ptrace-generic.h2012-08-03
> 01:38:10.0 +0200
> +++ linux-3.6-rc1
Dear uml-developers,
I have seen that in 3.6 rc1 the management of ptrace has been changed:
the functions in arch/um/kernel/ptrace.c now call the tracehooks.
I have seen that the return value of tracehook_report_syscall_entry has not
been taken into account.
(the return value should not be ignor
