From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: Denys Vlasenko <dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] ptrace(2): note SPARC deviation wrt get/set regs
Date: Mon, 23 Apr 2012 06:56:14 +1200 [thread overview]
Message-ID: <CAKgNAkgntJqu4UkeusJV-oak6ksM6_Y4z3GeYTfg0JD2tQ4jww@mail.gmail.com> (raw)
In-Reply-To: <1256454909-22861-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
[Adding some ptrace-knowledgeable people to CC]
Mike,
You long ago sent the patch below, but I didn't respond. I'm just
pulling up a few old ptrace pieces now for review.
Your patch below relates to PTRACE_GETREGS, PTRACE_GETFPREGS,
PTRACE_SETREGS, PTRACE_SETFPREGS. (The patch below no longer is
current, but is easy to fix)
Looking at arch/sparc/kernel/ptrace_32.c, I think I see what the point
of the patch is. However, the text is a bit cryptic. Would it not be
better to say something like
[[
Note that SPARC systems have the meaning of \fIdata\fP and \fIaddr\fP reversed;
that is, \fIdata\fP is ignored and the registers are copied to [from]
\fIaddr\fP.
]]
Cheers,
Michael
---------- Forwarded message ----------
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Date: Sun, Oct 25, 2009 at 8:15 PM
Subject: [PATCH] ptrace(2): note SPARC deviation wrt get/set regs
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Unfortunately the SPARC ptrace port handles the addr/data args the opposite
of every other arch. It expects the struct to be in addr and the data is
ignored.
Signed-off-by: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
---
man2/ptrace.2 | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 68601df..7cce955 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -168,6 +168,8 @@ respectively, to location \fIdata\fP in the parent.
See \fI<sys/user.h>\fP for information on
the format of this data.
(\fIaddr\fP is ignored.)
+
+Note that SPARC systems have the meaning of \fIdata\fP and \fIaddr\fP reversed.
.TP
.BR PTRACE_GETSIGINFO " (since Linux 2.3.99-pre6)"
Retrieve information about the signal that caused the stop.
@@ -184,6 +186,8 @@ As for
some general
purpose register modifications may be disallowed.
(\fIaddr\fP is ignored.)
+
+Note that SPARC systems have the meaning of \fIdata\fP and \fIaddr\fP reversed.
.TP
.BR PTRACE_SETSIGINFO " (since Linux 2.3.99-pre6)"
Set signal information.
--
1.6.5.1
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-22 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 7:15 [PATCH] ptrace(2): note SPARC deviation wrt get/set regs Mike Frysinger
[not found] ` <1256454909-22861-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2012-04-22 18:56 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <CAKgNAkgntJqu4UkeusJV-oak6ksM6_Y4z3GeYTfg0JD2tQ4jww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-24 3:55 ` Mike Frysinger
[not found] ` <201204232355.39879.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2012-04-24 6:05 ` Michael Kerrisk (man-pages)
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=CAKgNAkgntJqu4UkeusJV-oak6ksM6_Y4z3GeYTfg0JD2tQ4jww@mail.gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).