From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] arm: Early IRQ enabling in the Undef user handler
Date: Tue, 1 Apr 2014 16:41:42 +0100 [thread overview]
Message-ID: <20140401154142.GE20061@arm.com> (raw)
In-Reply-To: <CAKZGPAO4Fj=8cU3rYJBePBs_nbWdAW+5j5bO_F=jmqsxi7pYPg@mail.gmail.com>
On Tue, Apr 01, 2014 at 01:03:04PM +0100, Arun KS wrote:
> On Thu, Mar 13, 2014 at 11:45 PM, Catalin Marinas
> <catalin.marinas@arm.com> wrote:
> > I've had this series in my repo for a long time with some follow-ups on
> > the list but without any conclusive ACK or NAK. If there are no
> > objections, I plan to send it to the patch system.
> >
> > The only change is rebasing to 3.14-rc6 and adding some Cc for the
> > crunch bits.
> >
> > The __und_usr handler accesses the user space to read the opcode of the
> > faulting instruction. This is currently done with interrupts disabled
> > but it could potentially cause a data abort of the page table was
> > modified from another CPU. The data abort with interrupts disabled
> > triggers a might_sleep() warning in do_page_fault() or, worse, deadlock
> > on the pte lock when TLB ops broadcasting is enabled (ARM11MPCore or A15
> > together with workaround for erratum 798181).
> >
> > Catalin Marinas (5):
> > arm: Move asm macro get_thread_info to asm/assembler.h
> > arm: Add {inc,dec}_preempt_count asm macros
> > arm: Disable preemption in iwmmxt_task_enable()
> > arm: Disable preemption in crunch_task_enable()
> > arm: Enable IRQs before attempting to read user space in __und_usr
> >
> > arch/arm/include/asm/assembler.h | 42 ++++++++++++++++++++++++++++++++++++++
> > arch/arm/kernel/entry-armv.S | 11 ++++++----
> > arch/arm/kernel/entry-header.S | 11 ----------
> > arch/arm/kernel/iwmmxt.S | 15 ++++++++++----
> > arch/arm/mach-ep93xx/crunch-bits.S | 13 +++++++++---
> > arch/arm/vfp/entry.S | 28 ++++++++-----------------
> > arch/arm/vfp/vfphw.S | 19 ++++++-----------
> > 7 files changed, 84 insertions(+), 55 deletions(-)
>
> Tested-by: Arun KS<getarunks@gmail.com>
Thanks. I assume it's tested only with VFP (not crunch nor iwmmxt).
--
Catalin
next prev parent reply other threads:[~2014-04-01 15:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 18:15 [PATCH 0/5] arm: Early IRQ enabling in the Undef user handler Catalin Marinas
2014-03-13 18:15 ` [PATCH 1/5] arm: Move asm macro get_thread_info to asm/assembler.h Catalin Marinas
2014-03-13 18:15 ` [PATCH 2/5] arm: Add {inc,dec}_preempt_count asm macros Catalin Marinas
2014-03-13 18:15 ` [PATCH 3/5] arm: Disable preemption in iwmmxt_task_enable() Catalin Marinas
2014-04-10 9:14 ` Russell King - ARM Linux
2014-03-13 18:15 ` [PATCH 4/5] arm: Disable preemption in crunch_task_enable() Catalin Marinas
2014-04-10 9:14 ` Russell King - ARM Linux
2014-03-13 18:15 ` [PATCH 5/5] arm: Enable IRQs before attempting to read user space in __und_usr Catalin Marinas
2014-04-01 12:24 ` Arun KS
2014-04-01 14:48 ` Russell King - ARM Linux
2014-04-04 11:29 ` Arun KS
2014-04-04 15:42 ` Catalin Marinas
2014-04-01 12:03 ` [PATCH 0/5] arm: Early IRQ enabling in the Undef user handler Arun KS
2014-04-01 15:41 ` Catalin Marinas [this message]
2014-04-02 4:03 ` Arun KS
-- strict thread matches above, loose matches on Subject: below --
2013-08-28 11:34 Catalin Marinas
2014-03-31 4:11 ` Yang Zhang
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=20140401154142.GE20061@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 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).