From: Christoph Hellwig <hch@lst.de>
To: matthew@wil.cx
Cc: parisc-linux@parisc-linux.org
Subject: [parisc-linux] [RFC] parisc sys_ptrace prototype
Date: Mon, 19 Sep 2005 22:39:52 +0200 [thread overview]
Message-ID: <20050919203952.GA19511@lst.de> (raw)
parisc has a different prototype for ptrace in that it passes the
pid as pid_t, not as long. This doesn't matter on 32bit architectures
because both are 32bit, but it's different for 64bit kernel.
OTOH I've heard 64bit parisc userland is mostly non-existant so maybe
we could still fix this, greatly simplifying a later ptrace
consolidation.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/arch/parisc/kernel/ptrace.c
===================================================================
--- linux-2.6.orig/arch/parisc/kernel/ptrace.c 2005-09-18 13:46:52.000000000 +0200
+++ linux-2.6/arch/parisc/kernel/ptrace.c 2005-09-19 22:37:07.000000000 +0200
@@ -78,7 +78,7 @@
pa_psw(child)->l = 0;
}
-long sys_ptrace(long request, pid_t pid, long addr, long data)
+long sys_ptrace(long request, long pid, long addr, long data)
{
struct task_struct *child;
long ret;
Index: linux-2.6/include/asm-parisc/unistd.h
===================================================================
--- linux-2.6.orig/include/asm-parisc/unistd.h 2005-09-18 13:47:39.000000000 +0200
+++ linux-2.6/include/asm-parisc/unistd.h 2005-09-19 22:37:22.000000000 +0200
@@ -1005,7 +1005,7 @@
struct pt_regs *regs);
int sys_vfork(struct pt_regs *regs);
int sys_pipe(int *fildes);
-long sys_ptrace(long request, pid_t pid, long addr, long data);
+long sys_ptrace(long request, long pid, long addr, long data);
struct sigaction;
asmlinkage long sys_rt_sigaction(int sig,
const struct sigaction __user *act,
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
reply other threads:[~2005-09-19 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050919203952.GA19511@lst.de \
--to=hch@lst.de \
--cc=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.org \
/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