From: Mukesh Ojha <mojha@codeaurora.org>
To: Jann Horn <jannh@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Qiaowei Ren <qiaowei.ren@intel.com>
Subject: Re: [PATCH v2 4/4] x86/uaccess: Fix implicit cast of __user pointer
Date: Sat, 30 Mar 2019 01:57:12 +0530 [thread overview]
Message-ID: <dd654d81-7c04-91a9-7e78-f0e83e41f5f9@codeaurora.org> (raw)
In-Reply-To: <20190329163047.223508-4-jannh@google.com>
On 3/29/2019 10:00 PM, Jann Horn wrote:
> The first two arguments of __user_atomic_cmpxchg_inatomic() are:
>
> - `uval` is a kernel pointer into which the old value should be stored
> - `ptr` is the user pointer on which the cmpxchg should operate
>
> This means that casting `uval` to `__typeof__(ptr)` is wrong. Since `uval`
> is only used once inside the macro, just get rid of __uval and use `(uval)`
> directly.
>
> Signed-off-by: Jann Horn <jannh@google.com>
Looks good to me.
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> arch/x86/include/asm/uaccess.h | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/uaccess.h b/arch/x86/include/asm/uaccess.h
> index 1954dd5552a2..a21f2a2f17bf 100644
> --- a/arch/x86/include/asm/uaccess.h
> +++ b/arch/x86/include/asm/uaccess.h
> @@ -585,7 +585,6 @@ extern void __cmpxchg_wrong_size(void)
> #define __user_atomic_cmpxchg_inatomic(uval, ptr, old, new, size) \
> ({ \
> int __ret = 0; \
> - __typeof__(ptr) __uval = (uval); \
> __typeof__(*(ptr)) __old = (old); \
> __typeof__(*(ptr)) __new = (new); \
> __uaccess_begin_nospec(); \
> @@ -661,7 +660,7 @@ extern void __cmpxchg_wrong_size(void)
> __cmpxchg_wrong_size(); \
> } \
> __uaccess_end(); \
> - *__uval = __old; \
> + *(uval) = __old; \
> __ret; \
> })
>
prev parent reply other threads:[~2019-03-29 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 16:30 [PATCH v2 1/4] kernel.h: use parentheses around argument in u64_to_user_ptr() Jann Horn
2019-03-29 16:30 ` [PATCH v2 2/4] x86/microcode: Fix __user annotations around generic_load_microcode() Jann Horn
2019-03-29 16:30 ` [PATCH v2 3/4] x86/fpu: Fix __user annotations Jann Horn
2019-03-29 18:03 ` Luc Van Oostenryck
2019-03-29 19:25 ` Jann Horn
2019-03-29 19:42 ` Al Viro
2019-03-29 16:30 ` [PATCH v2 4/4] x86/uaccess: Fix implicit cast of __user pointer Jann Horn
2019-03-29 20:27 ` Mukesh Ojha [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=dd654d81-7c04-91a9-7e78-f0e83e41f5f9@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qiaowei.ren@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®