From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 70801] ptrace PEEKDATA API is incorrect
Date: Wed, 19 Feb 2014 11:39:13 +0000 [thread overview]
Message-ID: <bug-70801-11311-5oxd7xsYde@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-70801-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=70801
Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX
--- Comment #3 from Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Mike Frysinger from comment #1)
> it depends entirely on the arch. a bunch do as the man page describes. the
> generic ptrace layer is not used by a bunch.
>
> for example alpha/kernel/ptrace.c:
> case PTRACE_PEEKTEXT: /* read word at location addr. */
> case PTRACE_PEEKDATA:
> copied = access_process_vm(child, addr, &tmp, sizeof(tmp), 0);
> ret = -EIO;
> if (copied != sizeof(tmp))
> break;
>
> force_successful_syscall_return();
> ret = tmp;
> break;
>
> or ia64/kernel/ptrace.c:
> case PTRACE_PEEKTEXT:
> case PTRACE_PEEKDATA:
> /* read word at location addr */
> if (access_process_vm(child, addr, &data, sizeof(data), 0)
> != sizeof(data))
> return -EIO;
> /* ensure return value is not mistaken for error code */
> force_successful_syscall_return();
> return data;
>
> it's the API that strace uses:
> strace/util.c:
> u.val = ptrace(PTRACE_PEEKDATA, pid, (char *) addr, 0);
>
> the generic glibc ignores it too:
> glibc/misc/ptrace.c:
> case PTRACE_PEEKDATA:
> va_start(ap, request);
> pid = va_arg(ap, pid_t);
> addr = va_arg(ap, void *);
> va_end(ap);
> break;
>
> although apparently glibc's linux layer has been rewriting this silently:
> if (request > 0 && request < 4)
> data = &ret;
> ...
> if (res >= 0 && request > 0 && request < 4)
> {
> __set_errno (0);
> return ret;
> }
>
> where request {1,2,3} are PTRACE_PEEK{TEXT,DATA,USER}
Thanks for the above, Mike.
> as mentioned before, the man page is geared towards documenting the C
> library interface rather than the syscall one. so the current docs are
> correct. this could use noting in the NOTES section.
Yes. I've noted that point in various informal contexts (such as mailing
lists), and it's also hidden away here
https://www.kernel.org/doc/man-pages/todo.html#migrate_to_kernel_source . But,
like that info in the ptrace() page, it should be more obvious. I committed a
patch, https://www.kernel.org/doc/man-pages/todo.html#migrate_to_kernel_source
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
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:[~2014-02-19 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 19:31 [Bug 70801] New: ptrace PEEKDATA API is incorrect bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
[not found] ` <bug-70801-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2014-02-18 22:37 ` [Bug 70801] " bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2014-02-19 11:33 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2014-02-19 11:39 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
2014-02-24 21:26 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
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=bug-70801-11311-5oxd7xsYde@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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).