linux-kernel - Re: [patch] s390: Remove self ptrace IEEE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080430121538.GC28831@infradead.org>
Date:	Wed, 30 Apr 2008 08:15:38 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org
Cc:	Martin Schwidefsky <schwidefsky@...ibm.com>, akpm@....org
Subject: Re: [patch] s390: Remove self ptrace IEEE_IP hack.

And now that the last architecture (s390) has been converted to the
generic ptrace code the __ARCH_SYS_PTRACE ifdef can go away.  Once we've
also converted all architectures to compat_sys_ptrace some more code can
be made private to kernel/ptrace.c.

Signed-off-by: Christoph Hellwig <hch@....de>

Index: linux-2.6/kernel/ptrace.c
===================================================================
--- linux-2.6.orig/kernel/ptrace.c	2008-04-30 14:04:33.000000000 +0200
+++ linux-2.6/kernel/ptrace.c	2008-04-30 14:10:46.000000000 +0200
@@ -543,7 +543,6 @@ struct task_struct *ptrace_get_task_stru
 #define arch_ptrace_attach(child)	do { } while (0)
 #endif

-#ifndef __ARCH_SYS_PTRACE
 asmlinkage long sys_ptrace(long request, long pid, long addr, long data)
 {
 	struct task_struct *child;
@@ -591,7 +590,6 @@ asmlinkage long sys_ptrace(long request,
 	unlock_kernel();
 	return ret;
 }
-#endif /* __ARCH_SYS_PTRACE */

 int generic_ptrace_peekdata(struct task_struct *tsk, long addr, long data)
 {
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/