From: Christoph Hellwig <hch@infradead.org>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>, akpm@osd.org
Subject: Re: [patch] s390: Remove self ptrace IEEE_IP hack.
Date: Wed, 30 Apr 2008 08:15:38 -0400 [thread overview]
Message-ID: <20080430121538.GC28831@infradead.org> (raw)
In-Reply-To: <1209555393.10954.32.camel@localhost>
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@lst.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)
{
prev parent reply other threads:[~2008-04-30 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 9:14 [patch] s390: Remove self ptrace IEEE_IP hack Martin Schwidefsky
2008-04-30 9:19 ` Christoph Hellwig
2008-04-30 9:33 ` Martin Schwidefsky
2008-04-30 11:36 ` Martin Schwidefsky
2008-04-30 12:04 ` Christoph Hellwig
2008-04-30 12:15 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080430121538.GC28831@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osd.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox