From: mst@redhat.com (Michael S. Tsirkin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm64: Fix __addr_ok and __range_ok macros
Date: Thu, 6 Mar 2014 10:20:23 +0200 [thread overview]
Message-ID: <20140306082023.GA4160@redhat.com> (raw)
In-Reply-To: <1394059289-3972-1-git-send-email-cov@codeaurora.org>
On Wed, Mar 05, 2014 at 05:41:28PM -0500, Christopher Covington wrote:
> Without this, the following scenario is incorrectly determined
> to be invalid.
>
> addr 0x7f_ffffe000 size 8192 addr_limit 0x80_00000000
>
> This behavior was observed while trying to vmsplice the stack
> as part of a CRIU dump of a process.
>
> Signed-off-by: Christopher Covington <cov@codeaurora.org>
> ---
> arch/arm64/include/asm/uaccess.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/include/asm/uaccess.h b/arch/arm64/include/asm/uaccess.h
> index edb3d5c..9309024 100644
> --- a/arch/arm64/include/asm/uaccess.h
> +++ b/arch/arm64/include/asm/uaccess.h
> @@ -66,12 +66,12 @@ static inline void set_fs(mm_segment_t fs)
> #define segment_eq(a,b) ((a) == (b))
>
> /*
> - * Return 1 if addr < current->addr_limit, 0 otherwise.
> + * Return 1 if addr <= current->addr_limit, 0 otherwise.
> */
> #define __addr_ok(addr) \
> ({ \
> unsigned long flag; \
> - asm("cmp %1, %0; cset %0, lo" \
> + asm("cmp %1, %0; cset %0, ls" \
> : "=&r" (flag) \
> : "r" (addr), "0" (current_thread_info()->addr_limit) \
> : "cc"); \
BTW can this use mov %0, #0 like arch/arm/include/asm/uaccess.h does?
Would make it more portable ...
> @@ -83,7 +83,7 @@ static inline void set_fs(mm_segment_t fs)
> * Returns 1 if the range is valid, 0 otherwise.
> *
> * This is equivalent to the following test:
> - * (u65)addr + (u65)size < (u65)current->addr_limit
> + * (u65)addr + (u65)size <= current->addr_limit
> *
> * This needs 65-bit arithmetic.
> */
> @@ -91,7 +91,7 @@ static inline void set_fs(mm_segment_t fs)
> ({ \
> unsigned long flag, roksum; \
> __chk_user_ptr(addr); \
> - asm("adds %1, %1, %3; ccmp %1, %4, #2, cc; cset %0, cc" \
> + asm("adds %1, %1, %3; ccmp %1, %4, #3, cc; cset %0, ls" \
> : "=&r" (flag), "=&r" (roksum) \
> : "1" (addr), "Ir" (size), \
> "r" (current_thread_info()->addr_limit) \
> --
> Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> hosted by the Linux Foundation.
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christopher Covington <cov@codeaurora.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] arm64: Fix __addr_ok and __range_ok macros
Date: Thu, 6 Mar 2014 10:20:23 +0200 [thread overview]
Message-ID: <20140306082023.GA4160@redhat.com> (raw)
In-Reply-To: <1394059289-3972-1-git-send-email-cov@codeaurora.org>
On Wed, Mar 05, 2014 at 05:41:28PM -0500, Christopher Covington wrote:
> Without this, the following scenario is incorrectly determined
> to be invalid.
>
> addr 0x7f_ffffe000 size 8192 addr_limit 0x80_00000000
>
> This behavior was observed while trying to vmsplice the stack
> as part of a CRIU dump of a process.
>
> Signed-off-by: Christopher Covington <cov@codeaurora.org>
> ---
> arch/arm64/include/asm/uaccess.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/include/asm/uaccess.h b/arch/arm64/include/asm/uaccess.h
> index edb3d5c..9309024 100644
> --- a/arch/arm64/include/asm/uaccess.h
> +++ b/arch/arm64/include/asm/uaccess.h
> @@ -66,12 +66,12 @@ static inline void set_fs(mm_segment_t fs)
> #define segment_eq(a,b) ((a) == (b))
>
> /*
> - * Return 1 if addr < current->addr_limit, 0 otherwise.
> + * Return 1 if addr <= current->addr_limit, 0 otherwise.
> */
> #define __addr_ok(addr) \
> ({ \
> unsigned long flag; \
> - asm("cmp %1, %0; cset %0, lo" \
> + asm("cmp %1, %0; cset %0, ls" \
> : "=&r" (flag) \
> : "r" (addr), "0" (current_thread_info()->addr_limit) \
> : "cc"); \
BTW can this use mov %0, #0 like arch/arm/include/asm/uaccess.h does?
Would make it more portable ...
> @@ -83,7 +83,7 @@ static inline void set_fs(mm_segment_t fs)
> * Returns 1 if the range is valid, 0 otherwise.
> *
> * This is equivalent to the following test:
> - * (u65)addr + (u65)size < (u65)current->addr_limit
> + * (u65)addr + (u65)size <= current->addr_limit
> *
> * This needs 65-bit arithmetic.
> */
> @@ -91,7 +91,7 @@ static inline void set_fs(mm_segment_t fs)
> ({ \
> unsigned long flag, roksum; \
> __chk_user_ptr(addr); \
> - asm("adds %1, %1, %3; ccmp %1, %4, #2, cc; cset %0, cc" \
> + asm("adds %1, %1, %3; ccmp %1, %4, #3, cc; cset %0, ls" \
> : "=&r" (flag), "=&r" (roksum) \
> : "1" (addr), "Ir" (size), \
> "r" (current_thread_info()->addr_limit) \
> --
> Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-03-06 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 22:41 [RFC PATCH] arm64: Fix __addr_ok and __range_ok macros Christopher Covington
2014-03-05 22:41 ` Christopher Covington
2014-03-06 8:20 ` Michael S. Tsirkin [this message]
2014-03-06 8:20 ` Michael S. Tsirkin
2014-03-06 16:08 ` Will Deacon
2014-03-06 16:08 ` Will Deacon
2014-03-07 13:22 ` Christopher Covington
2014-03-07 13:22 ` Christopher Covington
2014-03-13 11:20 ` Catalin Marinas
2014-03-13 11:20 ` Catalin Marinas
2014-03-13 13:41 ` Christopher Covington
2014-03-13 13:41 ` Christopher Covington
2014-03-13 15:53 ` Catalin Marinas
2014-03-13 15:53 ` Catalin Marinas
2014-03-19 16:29 ` [PATCH v2] arm64: Fix __range_ok macro Christopher Covington
2014-03-19 16:29 ` Christopher Covington
2014-03-20 17:42 ` Catalin Marinas
2014-03-20 17:42 ` 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=20140306082023.GA4160@redhat.com \
--to=mst@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.