From: Oleg Nesterov <oleg@redhat.com>
To: Sargun Dhillon <sargun@sargun.me>
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, linux-api@vger.kernel.org,
linux-fsdevel@vger.kernel.org, tycho@tycho.ws, jannh@google.com,
cyphar@cyphar.com, christian.brauner@ubuntu.com,
luto@amacapital.net, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v2 4/4] samples: Add example of using PTRACE_GETFD in conjunction with user trap
Date: Mon, 9 Dec 2019 20:30:00 +0100 [thread overview]
Message-ID: <20191209192959.GB10721@redhat.com> (raw)
In-Reply-To: <20191209070646.GA32477@ircssh-2.c.rugged-nimbus-611.internal>
On 12/09, Sargun Dhillon wrote:
>
> +#define CHILD_PORT_TRY_BIND 80
> +#define CHILD_PORT_ACTUAL_BIND 4998
...
> +static int handle_req(int listener)
> +{
> + struct sockaddr_in addr = {
> + .sin_family = AF_INET,
> + .sin_port = htons(4998),
then I think
.sin_port = htons(CHILD_PORT_ACTUAL_BIND);
would be more clear...
> + .sin_addr = {
> + .s_addr = htonl(INADDR_LOOPBACK)
> + }
> + };
> + struct ptrace_getfd_args getfd_args = {
> + .options = PTRACE_GETFD_O_CLOEXEC
> + };
> + struct seccomp_notif_sizes sizes;
> + struct seccomp_notif_resp *resp;
> + struct seccomp_notif *req;
> + int fd, ret = 1;
> +
> + if (seccomp(SECCOMP_GET_NOTIF_SIZES, 0, &sizes) < 0) {
> + perror("seccomp(GET_NOTIF_SIZES)");
> + goto out;
> + }
> + req = malloc(sizes.seccomp_notif);
> + if (!req)
> + goto out;
> + memset(req, 0, sizeof(*req));
> +
> + resp = malloc(sizes.seccomp_notif_resp);
> + if (!resp)
> + goto out_free_req;
> + memset(resp, 0, sizeof(*resp));
> +
> + if (ioctl(listener, SECCOMP_IOCTL_NOTIF_RECV, req)) {
> + perror("ioctl recv");
> + goto out;
> + }
> + printf("Child tried to call bind with fd: %lld\n", req->data.args[0]);
> + getfd_args.fd = req->data.args[0];
> + fd = ptrace_getfd(req->pid, &getfd_args);
and iiuc otherwise you do not need to ptrace the child. So you could remove
ptrace(PTRACE_SEIZE) in main() and just do
ptrace(PTRACE_SEIZE, req->pid);
fd = ptrace_getfd(req->pid, &getfd_args);
ptrace(PTRACE_DETACH, req->pid);
here. However, PTRACE_DETACH won't work, it needs the stopped tracee. We can
add PTRACE_DETACH_ASYNC, but this makes me think that PTRACE_GETFD has nothing
to do with ptrace.
May be a new syscall which does ptrace_may_access() + get_task_file() will make
more sense?
Oleg.
next prev parent reply other threads:[~2019-12-09 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 7:06 [PATCH v2 4/4] samples: Add example of using PTRACE_GETFD in conjunction with user trap Sargun Dhillon
2019-12-09 19:30 ` Oleg Nesterov [this message]
2019-12-09 19:49 ` Christian Brauner
2019-12-09 20:46 ` Oleg Nesterov
2019-12-10 11:10 ` Christian Brauner
2019-12-10 15:35 ` Tycho Andersen
2019-12-10 16:07 ` Sargun Dhillon
2019-12-10 16:13 ` Tycho Andersen
2019-12-10 16:38 ` Christian Brauner
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=20191209192959.GB10721@redhat.com \
--to=oleg@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=containers@lists.linux-foundation.org \
--cc=cyphar@cyphar.com \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=sargun@sargun.me \
--cc=tycho@tycho.ws \
--cc=viro@zeniv.linux.org.uk \
/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).