From: Oleg Nesterov <oleg@redhat.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Andy Lutomirski <luto@kernel.org>,
Elvira Khabirova <lineprinter@altlinux.org>,
Eugene Syromyatnikov <esyr@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Kees Cook <keescook@chromium.org>,
Jann Horn <jannh@google.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
strace-devel@lists.strace.io
Subject: Re: [PATCH v4 2/2] ptrace: add PTRACE_GET_SYSCALL_INFO request
Date: Wed, 28 Nov 2018 15:29:30 +0100 [thread overview]
Message-ID: <20181128142930.GF30395@redhat.com> (raw)
In-Reply-To: <20181128141049.GD30395@redhat.com>
On 11/28, Oleg Nesterov wrote:
>
> On 11/28, Dmitry V. Levin wrote:
> >
> > +static unsigned long
> > +ptrace_get_syscall_info_entry(struct task_struct *child,
> > + struct ptrace_syscall_info *info)
> > +{
> > + struct pt_regs *regs = task_pt_regs(child);
> > + unsigned long args[ARRAY_SIZE(info->entry.args)];
> > + int i;
> > +
> > + info->op = PTRACE_SYSCALL_INFO_ENTRY;
> > + info->arch = syscall_get_arch(child);
> > + info->entry.nr = syscall_get_nr(child, regs);
> > + info->entry.instruction_pointer = instruction_pointer(regs);
> > + info->entry.stack_pointer = user_stack_pointer(regs);
> > + info->entry.frame_pointer = frame_pointer(regs);
> > + syscall_get_arguments(child, regs, 0, ARRAY_SIZE(args), args);
> > + for (i = 0; i < ARRAY_SIZE(args); i++)
> > + info->entry.args[i] = args[i];
>
> I must have missed something,
Yes ;) I didn't look at info->entry.args, it is __u64[6].
> but why do we need the temporary args[],
> syscall_get_arguments(..., info->entry.args) should equally work?
>
> Oleg.
prev parent reply other threads:[~2018-11-28 14:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 13:04 [PATCH v4 0/2] ptrace: add PTRACE_GET_SYSCALL_INFO request Dmitry V. Levin
[not found] ` <20181128130439.GB28206-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
2018-11-28 13:06 ` [PATCH v4 1/2] ptrace: save the type of syscall-stop in ptrace_message Dmitry V. Levin
2018-11-28 13:49 ` Oleg Nesterov
2018-11-28 14:05 ` Dmitry V. Levin
2018-11-28 14:20 ` Oleg Nesterov
[not found] ` <20181128142006.GE30395-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-11-28 15:23 ` Dmitry V. Levin
[not found] ` <20181128152346.GG28206-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
2018-11-28 22:11 ` Dmitry V. Levin
2018-11-28 23:17 ` Andy Lutomirski
2018-11-29 10:34 ` Dmitry V. Levin
2018-11-29 15:03 ` Oleg Nesterov
2018-11-29 14:47 ` Oleg Nesterov
[not found] ` <20181129144742.GB10645-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-11-29 21:10 ` Dmitry V. Levin
2018-11-30 11:29 ` Oleg Nesterov
[not found] ` <20181130112920.GD23670-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-11-30 22:53 ` Dmitry V. Levin
2018-11-28 13:07 ` [PATCH v4 2/2] ptrace: add PTRACE_GET_SYSCALL_INFO request Dmitry V. Levin
2018-11-28 14:10 ` Oleg Nesterov
2018-11-28 14:29 ` Oleg Nesterov [this message]
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=20181128142930.GF30395@redhat.com \
--to=oleg@redhat.com \
--cc=esyr@redhat.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=ldv@altlinux.org \
--cc=lineprinter@altlinux.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=rostedt@goodmis.org \
--cc=strace-devel@lists.strace.io \
/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).