linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: check for number of arguments in syscall_get/set_arguments()
Date: Wed, 2 Oct 2013 11:46:26 +0100	[thread overview]
Message-ID: <20131002104625.GF28311@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <524BC11D.2050003@linaro.org>

On Wed, Oct 02, 2013 at 07:45:49AM +0100, AKASHI Takahiro wrote:
> On 10/01/2013 06:19 PM, Will Deacon wrote:
> > On Tue, Oct 01, 2013 at 06:33:04AM +0100, AKASHI Takahiro wrote:
> >> In ftrace_syscall_enter(),
> >>      syscall_get_arguments(..., 0, n, ...)
> >> 	if (i == 0) { <handle orig_x0> ...; n--;}
> >> 	memcpy(..., n * sizeof(args[0]));
> >> If 'number of arguments(n)' is zero and 'argument index(i)' is also zero in
> >> syscall_get_arguments(), none of arguments should be copied by memcpy().
> >> Otherwise 'n--' can be a big positive number and unexpected amount of data
> >> will be copied. Tracing system calls which take no argument, say sync(void),
> >> may hit this case and eventually make the system corrupted.
> >> This patch fixes the issue both in syscall_get_arguments() and
> >> syscall_set_arguments().
> >>
> >> Please note, however, that asm-generic/syscall.h says,
> >>   * syscall_get_arguments - extract system call parameter values
> >>   * @i:          argument index [0,5]
> >>   * @n:          number of arguments; n+i must be [1,6].
> >> and so we'd better change the caller's code(ftrace_syscall_enter).
> >
> > Since (most) other architectures deal with n+i == 0, please can you submit a
> > separate patch updating that comment?
> 
> Yes, I will. But is the patch that only modifies a comment acceptable?

Well, if the comment is wrong is should either be fixed or removed. Leaving
it alone just serves to confuse other architectures trying to implement the
backend API.

Of course, if the comment is *correct*, then the tracer is broken, but we
can have that discussion off the back of the patch (just be sure to CC the
right people).

> > Looks sensible. Please can you fix arch/arm/ as well?
> 
> Yes, I will.

Thanks!

Will

      reply	other threads:[~2013-10-02 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01  5:33 [PATCH] arm64: check for number of arguments in syscall_get/set_arguments() AKASHI Takahiro
2013-10-01  9:19 ` Will Deacon
2013-10-02  6:45   ` AKASHI Takahiro
2013-10-02 10:46     ` Will Deacon [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=20131002104625.GF28311@mudshark.cambridge.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).