From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: adjust el0_sync so that a function can be called
Date: Tue, 29 Apr 2014 10:42:11 +0100 [thread overview]
Message-ID: <20140429094211.GC17007@arm.com> (raw)
In-Reply-To: <1398627854-9617-2-git-send-email-larry.bassel@linaro.org>
On Sun, Apr 27, 2014 at 08:44:12PM +0100, Larry Bassel wrote:
> diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
> index 39ac630..eda7755 100644
> --- a/arch/arm64/kernel/entry.S
> +++ b/arch/arm64/kernel/entry.S
[...]
> @@ -421,28 +421,30 @@ el0_da:
> /*
> * Data abort handling
> */
> - mrs x0, far_el1
> - bic x0, x0, #(0xff << 56)
> disable_step x1
> isb
> enable_dbg
> // enable interrupts before calling the main handler
> enable_irq
> + mrs x0, far_el1
> + bic x0, x0, #(0xff << 56)
> mov x1, x25
> mov x2, sp
> + adr lr, ret_from_exception
> b do_mem_abort
Reading the far_el1 after enable_dbg and enable_irq is racy, we can no
longer guarantee its value in the original data abort context.
> el0_ia:
> /*
> * Instruction abort handling
> */
> - mrs x0, far_el1
> disable_step x1
> isb
> enable_dbg
> // enable interrupts before calling the main handler
> enable_irq
> + mrs x0, far_el1
> orr x1, x25, #1 << 24 // use reserved ISS bit for instruction aborts
> mov x2, sp
> + adr lr, ret_from_exception
> b do_mem_abort
> el0_fpsimd_acc:
Same here.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Larry Bassel <larry.bassel@linaro.org>
Cc: Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"khilman@linaro.org" <khilman@linaro.org>
Subject: Re: [PATCH 1/3] arm64: adjust el0_sync so that a function can be called
Date: Tue, 29 Apr 2014 10:42:11 +0100 [thread overview]
Message-ID: <20140429094211.GC17007@arm.com> (raw)
In-Reply-To: <1398627854-9617-2-git-send-email-larry.bassel@linaro.org>
On Sun, Apr 27, 2014 at 08:44:12PM +0100, Larry Bassel wrote:
> diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S
> index 39ac630..eda7755 100644
> --- a/arch/arm64/kernel/entry.S
> +++ b/arch/arm64/kernel/entry.S
[...]
> @@ -421,28 +421,30 @@ el0_da:
> /*
> * Data abort handling
> */
> - mrs x0, far_el1
> - bic x0, x0, #(0xff << 56)
> disable_step x1
> isb
> enable_dbg
> // enable interrupts before calling the main handler
> enable_irq
> + mrs x0, far_el1
> + bic x0, x0, #(0xff << 56)
> mov x1, x25
> mov x2, sp
> + adr lr, ret_from_exception
> b do_mem_abort
Reading the far_el1 after enable_dbg and enable_irq is racy, we can no
longer guarantee its value in the original data abort context.
> el0_ia:
> /*
> * Instruction abort handling
> */
> - mrs x0, far_el1
> disable_step x1
> isb
> enable_dbg
> // enable interrupts before calling the main handler
> enable_irq
> + mrs x0, far_el1
> orr x1, x25, #1 << 24 // use reserved ISS bit for instruction aborts
> mov x2, sp
> + adr lr, ret_from_exception
> b do_mem_abort
> el0_fpsimd_acc:
Same here.
--
Catalin
next prev parent reply other threads:[~2014-04-29 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 19:44 [PATCH 0/3] context tracker support for arm64 Larry Bassel
2014-04-27 19:44 ` Larry Bassel
2014-04-27 19:44 ` [PATCH 1/3] arm64: adjust el0_sync so that a function can be called Larry Bassel
2014-04-27 19:44 ` Larry Bassel
2014-04-29 9:42 ` Catalin Marinas [this message]
2014-04-29 9:42 ` Catalin Marinas
2014-05-05 22:44 ` Kevin Hilman
2014-05-05 22:44 ` Kevin Hilman
2014-04-27 19:44 ` [PATCH 2/3] arm64: add support for context tracking Larry Bassel
2014-04-27 19:44 ` Larry Bassel
2014-04-27 19:44 ` [PATCH 3/3] arm64: enable " Larry Bassel
2014-04-27 19:44 ` Larry Bassel
2014-04-29 9:43 ` Catalin Marinas
2014-04-29 9:43 ` 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=20140429094211.GC17007@arm.com \
--to=catalin.marinas@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 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.