From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: avoid multiple evaluation of ptr in get_user/put_user()
Date: Wed, 25 Sep 2013 18:29:52 +0900 [thread overview]
Message-ID: <5242AD10.3070001@linaro.org> (raw)
In-Reply-To: <20130924142553.GG25907@arm.com>
Catalin,
Thank you for your comments, and let me send a revised patch again
because my original message didn't reach MLs due to my screw-up.
BTW, I will submit a patch of ftrace support on arm64 once gcc supports
gprof (-pg) options.
-Takahiro AKASHI
On 09/24/2013 11:25 PM, Catalin Marinas wrote:
> On Tue, Sep 24, 2013 at 10:00:50AM +0100, AKASHI Takahiro wrote:
>> get_user() is defined as a function macro in arm64, and trace_get_user()
>> calls it as followed:
>> get_user(ch, ptr++);
>> Since the second parameter occurs twice in the definition, 'ptr++' is
>> unexpectedly evaluated twice and trace_get_user() will generate a bogus
>> string from user-provided one. As a result, some ftrace sysfs operations,
>> like "echo FUNCNAME > set_ftrace_filter," hit this case and eventually fail.
>> This patch fixes the issue both in get_user() and put_user().
>>
>> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
>> ---
>> arch/arm64/include/asm/uaccess.h | 12 ++++++++----
>> 1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/arm64/include/asm/uaccess.h b/arch/arm64/include/asm/uaccess.h
>> index edb3d5c..bbeab83 100644
>> --- a/arch/arm64/include/asm/uaccess.h
>> +++ b/arch/arm64/include/asm/uaccess.h
>> @@ -166,9 +166,11 @@ do { \
>> #define get_user(x, ptr) \
>> ({ \
>> + __typeof__(*(ptr)) *optr = (ptr); \
>> + \
>> might_fault(); \
>> - access_ok(VERIFY_READ, (ptr), sizeof(*(ptr))) ? \
>> - __get_user((x), (ptr)) : \
>> + access_ok(VERIFY_READ, optr, sizeof(*optr)) ? \
>> + __get_user((x), optr) : \
>> ((x) = 0, -EFAULT); \
>> })
>> @@ -227,9 +229,11 @@ do { \
>> #define put_user(x, ptr) \
>> ({ \
>> + __typeof__(*(ptr)) *optr = (ptr); \
>> + \
>> might_fault(); \
>> - access_ok(VERIFY_WRITE, (ptr), sizeof(*(ptr))) ? \
>> - __put_user((x), (ptr)) : \
>> + access_ok(VERIFY_WRITE, optr, sizeof(*optr)) ? \
>> + __put_user((x), optr) : \
>> -EFAULT; \
>> })
>> -- 1.7.9.5
>
> BTW, please use git send-email or other email client, the diff above is
> heavily corrupted (too many spaces at the beginning of the line, removed
> empty lines; I managed to fix it up this time but only because it was a
> small patch).
>
next prev parent reply other threads:[~2013-09-25 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 9:00 [PATCH] arm64: avoid multiple evaluation of ptr in get_user/put_user() AKASHI Takahiro
2013-09-24 14:05 ` Catalin Marinas
2013-09-24 14:25 ` Catalin Marinas
2013-09-25 9:29 ` AKASHI Takahiro [this message]
2013-09-25 13:21 ` Catalin Marinas
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=5242AD10.3070001@linaro.org \
--to=takahiro.akashi@linaro.org \
--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).