The patch titled
x86_64: Don't do syscall exit tracing twice
has been added to the -mm tree. Its filename is
x86_64-dont-do-syscall-exit-tracing-twice.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: x86_64: Don't do syscall exit tracing twice
From: "Andi Kleen" <ak@xxxxxxx>
int_ret_from_syscall already does syscall exit tracing, so no need to do it
again in the caller.
This caused problems for UML and some other special programs doing syscall
interception.
Signed-off-by: Andi Kleen <ak@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
arch/x86_64/kernel/entry.S | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff -puN arch/x86_64/kernel/entry.S~x86_64-dont-do-syscall-exit-tracing-twice arch/x86_64/kernel/entry.S
--- devel/arch/x86_64/kernel/entry.S~x86_64-dont-do-syscall-exit-tracing-twice 2006-05-29 14:16:26.000000000 -0700
+++ devel-akpm/arch/x86_64/kernel/entry.S 2006-05-29 14:16:26.000000000 -0700
@@ -281,12 +281,7 @@ tracesys:
ja 1f
movq %r10,%rcx /* fixup for C */
call *sys_call_table(,%rax,8)
- movq %rax,RAX-ARGOFFSET(%rsp)
-1: SAVE_REST
- movq %rsp,%rdi
- call syscall_trace_leave
- RESTORE_TOP_OF_STACK %rbx
- RESTORE_REST
+1: movq %rax,RAX-ARGOFFSET(%rsp)
/* Use IRET because user could have changed frame */
jmp int_ret_from_sys_call
CFI_ENDPROC
_
Patches currently in -mm which might be from ak@xxxxxxx are
x86_64-fix-stack-mmap-randomization-for-compat.patch
x86_64-fix-no-iommu-warning-in-pci-gart-driver.patch
i386-apic=-command-line-option-should-always-be.patch
x86_64-fix-last_tsc-calculation-of-pm-timer.patch
x86_64-handle-empty-node-zero.patch
x86_64-fix-off-by-one-in-bad_addr-checking-in.patch
x86_64-dont-do-syscall-exit-tracing-twice.patch
git-acpi.patch
git-agpgart.patch
x86_64-dont-warn-for-overflow-in-nommu-case-when-dma_mask-is-32bit-fix.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
