From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Cc: dje@google.com
Subject: Re: [PATCH] PR gdb/16188: Verify PTRACE_TRACEME succeeded
Date: Mon, 20 Feb 2017 12:19:00 -0000 [thread overview]
Message-ID: <e43135bc-c07b-25dd-cae7-3d146d490d4b@redhat.com> (raw)
In-Reply-To: <20170218050900.31399-1-sergiodj@redhat.com>
Hi Sergio,
This LGTM, save for the errno handling in Darwin bits:
On 02/18/2017 05:09 AM, Sergio Durigan Junior wrote:
> diff --git a/gdb/darwin-nat.c b/gdb/darwin-nat.c
> index 8c5e8a0..e02e51d 100644
> --- a/gdb/darwin-nat.c
> +++ b/gdb/darwin-nat.c
> @@ -254,7 +254,6 @@ darwin_ptrace (const char *name,
> {
> int ret;
>
> - errno = 0;
> ret = ptrace (request, pid, arg3, arg4);
> if (ret == -1 && errno == 0)
> ret = 0;
Removing "errno = 0" here is incorrect. There are ptrace calls where a -1
return is not an error, thus that check for "errno==0" after the
ptrace call. Since system calls are not required to clear errno on
success, that errno=0 is required.
This is Darwin, but the Linux man pages, in "man ptrace" say:
On error, all requests return -1, and errno is set appropriately. Since the
value returned by a successful PTRACE_PEEK* request may be -1, the caller
must clear errno before the call, and then check it afterward to determine whether
or not an error occurred.
And actually, the comment just above darwin_ptrace talks
about clearning errno. So it's really incorrect.
> @@ -1728,23 +1727,30 @@ darwin_ptrace_me (void)
> int res;
> char c;
>
> + errno = 0;
OTOH, I don't see the need to clear it here. Below,
errno will only be used when a syscall fails, and in
failure case, the syscall must set errno.
> /* Close write end point. */
> - close (ptrace_fds[1]);
> + if (close (ptrace_fds[1]) < 0)
> + trace_start_error_with_name ("close");
>
> /* Wait until gdb is ready. */
> res = read (ptrace_fds[0], &c, 1);
> if (res != 0)
> - error (_("unable to read from pipe, read returned: %d"), res);
> - close (ptrace_fds[0]);
> + trace_start_error (_("unable to read from pipe, read returned: %d"), res);
> +
> + if (close (ptrace_fds[0]) < 0)
> + trace_start_error_with_name ("close");
>
> /* Get rid of privileges. */
> - setegid (getgid ());
> + if (setegid (getgid ()) < 0)
> + trace_start_error_with_name ("setegid");
>
> /* Set TRACEME. */
> - PTRACE (PT_TRACE_ME, 0, 0, 0);
> + if (PTRACE (PT_TRACE_ME, 0, 0, 0) < 0)
> + trace_start_error_with_name ("PTRACE");
>
> /* Redirect signals to exception port. */
> - PTRACE (PT_SIGEXC, 0, 0, 0);
> + if (PTRACE (PT_SIGEXC, 0, 0, 0) < 0)
> + trace_start_error_with_name ("PTRACE");
> }
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-02-20 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 20:19 Sergio Durigan Junior
2017-02-17 10:48 ` Pedro Alves
2017-02-18 4:55 ` Sergio Durigan Junior
2017-02-18 5:09 ` Sergio Durigan Junior
2017-02-20 12:19 ` Pedro Alves [this message]
2017-02-20 12:51 ` Sergio Durigan Junior
2017-02-20 13:05 ` [PATCH] Fix thinko on last commit Sergio Durigan Junior
2017-02-20 13:08 ` Sergio Durigan Junior
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=e43135bc-c07b-25dd-cae7-3d146d490d4b@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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