Thread (1 message) 1 message, 1 author, 2014-02-18

[Bug 70801] ptrace PEEKDATA API is incorrect

From: <hidden>
Date: 2014-02-18 22:37:00

Possibly related (same subject, not in this thread)

https://bugzilla.kernel.org/show_bug.cgi?id=70801

Mike Frysinger [off-list ref] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org
--- Comment #1 from Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org> ---
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}

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.

-- 
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help