From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Niklas Cassel <niklas.cassel@linaro.org>
Cc: Andy Gross <andy.gross@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: qcom: scm: Fix crash in qcom_scm_call_atomic1()
Date: Tue, 10 Apr 2018 11:58:54 -0700 [thread overview]
Message-ID: <20180410185854.GB23948@tuxbook-pro> (raw)
In-Reply-To: <20180409214016.21219-1-niklas.cassel@linaro.org>
On Mon 09 Apr 14:40 PDT 2018, Niklas Cassel wrote:
> qcom_scm_call_atomic1() can crash with a NULL pointer dereference at
> qcom_scm_call_atomic1+0x30/0x48.
>
> disassembly of qcom_scm_call_atomic1():
> ...
> <0xc08d73b0 <+12>: ldr r3, [r12]
> ... (no instruction explicitly modifies r12)
> 0xc08d73cc <+40>: smc 0
> ... (no instruction explicitly modifies r12)
> 0xc08d73d4 <+48>: ldr r3, [r12] <- crashing instruction
> ...
>
> Since the first ldr is successful, and since r12 isn't explicitly
> modified by any instruction between the first and the second ldr,
> it must have been modified by the smc call, which is ok,
> since r12 is caller save according to the AAPCS.
>
> Add r12 to the clobber list so that the compiler knows that the
> callee potentially overwrites the value in r12.
> Clobber descriptions may not in any way overlap with an input or
> output operand.
>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> Signed-off-by: Niklas Cassel <niklas.cassel@linaro.org>
> ---
> drivers/firmware/qcom_scm-32.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/firmware/qcom_scm-32.c b/drivers/firmware/qcom_scm-32.c
> index dfbd894d5bb7..4e24e591ae74 100644
> --- a/drivers/firmware/qcom_scm-32.c
> +++ b/drivers/firmware/qcom_scm-32.c
> @@ -147,7 +147,7 @@ static u32 smc(u32 cmd_addr)
> "smc #0 @ switch to secure world\n"
> : "=r" (r0)
> : "r" (r0), "r" (r1), "r" (r2)
> - : "r3");
> + : "r3", "r12");
> } while (r0 == QCOM_SCM_INTERRUPTED);
>
> return r0;
> @@ -263,7 +263,7 @@ static s32 qcom_scm_call_atomic1(u32 svc, u32 cmd, u32 arg1)
> "smc #0 @ switch to secure world\n"
> : "=r" (r0)
> : "r" (r0), "r" (r1), "r" (r2)
> - : "r3");
> + : "r3", "r12");
> return r0;
> }
>
> @@ -298,7 +298,7 @@ static s32 qcom_scm_call_atomic2(u32 svc, u32 cmd, u32 arg1, u32 arg2)
> "smc #0 @ switch to secure world\n"
> : "=r" (r0)
> : "r" (r0), "r" (r1), "r" (r2), "r" (r3)
> - );
> + : "r12");
> return r0;
> }
>
> @@ -328,7 +328,7 @@ u32 qcom_scm_get_version(void)
> "smc #0 @ switch to secure world\n"
> : "=r" (r0), "=r" (r1)
> : "r" (r0), "r" (r1)
> - : "r2", "r3");
> + : "r2", "r3", "r12");
> } while (r0 == QCOM_SCM_INTERRUPTED);
>
> version = r1;
> --
> 2.14.3
>
next prev parent reply other threads:[~2018-04-10 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 21:40 Niklas Cassel
2018-04-10 18:58 ` Bjorn Andersson [this message]
2018-04-11 1:55 ` Stephen Boyd
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=20180410185854.GB23948@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=akdwived@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
--cc=sboyd@codeaurora.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®