From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 1/6] arm64: ptrace: add NT_ARM_SYSTEM_CALL regset
Date: Wed, 26 Nov 2014 12:41:28 +0000 [thread overview]
Message-ID: <20141126124128.GH14866@arm.com> (raw)
In-Reply-To: <1416977391-24231-2-git-send-email-takahiro.akashi@linaro.org>
Hi Akashi,
On Wed, Nov 26, 2014 at 04:49:46AM +0000, AKASHI Takahiro wrote:
> This regeset is intended to be used to get and set a system call number
> while tracing.
> There was some discussion about possible approaches to do so:
>
> (1) modify x8 register with ptrace(PTRACE_SETREGSET) indirectly,
> and update regs->syscallno later on in syscall_trace_enter(), or
> (2) define a dedicated regset for this purpose as on s390, or
> (3) support ptrace(PTRACE_SET_SYSCALL) as on arch/arm
>
> Thinking of the fact that user_pt_regs doesn't expose 'syscallno' to
> tracer as well as that secure_computing() expects a changed syscall number,
> especially case of -1, to be visible before this function returns in
> syscall_trace_enter(), (1) doesn't work well.
> We will take (2) since it looks much cleaner.
>
> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> ---
> arch/arm64/kernel/ptrace.c | 35 +++++++++++++++++++++++++++++++++++
> include/uapi/linux/elf.h | 1 +
> 2 files changed, 36 insertions(+)
>
> diff --git a/arch/arm64/kernel/ptrace.c b/arch/arm64/kernel/ptrace.c
> index 8a4ae8e..8b98781 100644
> --- a/arch/arm64/kernel/ptrace.c
> +++ b/arch/arm64/kernel/ptrace.c
> @@ -551,6 +551,32 @@ static int tls_set(struct task_struct *target, const struct user_regset *regset,
> return ret;
> }
>
> +static int system_call_get(struct task_struct *target,
> + const struct user_regset *regset,
> + unsigned int pos, unsigned int count,
> + void *kbuf, void __user *ubuf)
> +{
> + struct pt_regs *regs = task_pt_regs(target);
> +
> + return user_regset_copyout(&pos, &count, &kbuf, &ubuf,
> + ®s->syscallno, 0, -1);
Does this work for big-endian machines? regs->syscallno is a u64, but the
regset defines it as an int. I think you need to copy to a temporary
register first.
Will
next prev parent reply other threads:[~2014-11-26 12:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 4:49 [PATCH v9 0/6] arm64: add seccomp support AKASHI Takahiro
2014-11-26 4:49 ` [PATCH v9 1/6] arm64: ptrace: add NT_ARM_SYSTEM_CALL regset AKASHI Takahiro
2014-11-26 12:41 ` Will Deacon [this message]
2014-11-27 5:53 ` AKASHI Takahiro
2014-11-27 14:10 ` Will Deacon
2014-11-28 5:25 ` AKASHI Takahiro
2014-11-26 4:49 ` [PATCH v9 2/6] arm64: ptrace: allow tracer to skip a system call AKASHI Takahiro
2014-11-26 13:02 ` Will Deacon
2014-11-27 6:46 ` AKASHI Takahiro
2014-11-27 10:07 ` Will Deacon
2014-11-26 4:49 ` [PATCH v9 3/6] asm-generic: add generic seccomp.h for secure computing mode 1 AKASHI Takahiro
2014-11-26 4:49 ` [PATCH v9 4/6] arm64: add seccomp syscall for compat task AKASHI Takahiro
2014-11-26 4:49 ` [PATCH v9 5/6] arm64: add SIGSYS siginfo " AKASHI Takahiro
2014-11-26 4:49 ` [PATCH v9 6/6] arm64: add seccomp support AKASHI Takahiro
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=20141126124128.GH14866@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).