From: alex.shi@linaro.org (Alex Shi)
To: linux-arm-kernel@lists.infradead.org
Subject: do page fault in atomic bug on arm
Date: Sun, 26 Nov 2017 23:23:42 +0800 [thread overview]
Message-ID: <c26314ab-90c0-cb04-4c55-ebcf2a7045e4@linaro.org> (raw)
In-Reply-To: <17ed7101-f076-f68c-b8f3-7cc62d24a641@linaro.org>
Sorry, this patch should be passed off, since we got your new fixing
patches. I shouldn't mentioned here.
Regards
Alex
On 11/26/2017 10:58 PM, Alex Shi wrote:
>> Can you try the following patch to try and catch the problem earlier?
>> I haven't tested it myself, and adding code may move things around in
>> the kernel and make this bug disappear.
> Do we still need to try this patch? I saw you tried it and do further more.
>> diff --git a/arch/arm/kernel/entry-header.S b/arch/arm/kernel/entry-header.S
>> index d523cd8439a3..ff577177b286 100644
>> --- a/arch/arm/kernel/entry-header.S
>> +++ b/arch/arm/kernel/entry-header.S
>> @@ -299,6 +299,8 @@
>> @ ARM mode restore
>> mov r2, sp
>> ldr r1, [r2, #\offset + S_PSR] @ get calling cpsr
>> + tst r1, #0xcf
>> + bne oops
>> ldr lr, [r2, #\offset + S_PC]! @ get pc
>> msr spsr_cxsf, r1 @ save in spsr_svc
>> #if defined(CONFIG_CPU_V6) || defined(CONFIG_CPU_32v6K)
>> @@ -314,6 +316,15 @@
>> @ after ldm {}^
>> add sp, sp, #\offset + PT_REGS_SIZE
>> movs pc, lr @ return & move spsr_svc into cpsr
>> +oops: .word 0xe7f001f2
> This oops cause allnoconfig with arm failed in build. but it's fine for
> a multi_v7_defconfig
> arch/arm/kernel/entry-common.S:106: Error: symbol `oops' is already defined
>
>> + .pushsection .rodata.str, "aMS", %progbits, 1
>> +2: .asciz "Returning to usermode but unexpected PSR bits set?"
>> + .popsection
>> + .pushsection __bug_table, "aw"
>> + .align 2
>> + .word oops, 2b
>> + .hword \@
>> + .popsection
>> #elif defined(CONFIG_CPU_V7M)
>> @ V7M restore.
>> @ Note that we don't need to do clrex here as clearing the local
next prev parent reply other threads:[~2017-11-26 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 13:06 do page fault in atomic bug on arm Alex Shi
2017-11-21 13:20 ` Russell King - ARM Linux
2017-11-24 15:09 ` Alex Shi
2017-11-24 15:56 ` Russell King - ARM Linux
2017-11-26 14:58 ` Alex Shi
2017-11-26 15:23 ` Alex Shi [this message]
2017-11-24 19:27 ` Russell King - ARM Linux
2017-11-24 20:25 ` Russell King - ARM Linux
2017-11-24 22:20 ` Russell King - ARM Linux
2017-11-26 15:02 ` Alex Shi
2017-11-26 14:59 ` Alex Shi
2017-11-27 1:40 ` Masami Hiramatsu
2017-11-27 13:36 ` Andrew Lunn
2017-11-27 13:55 ` Russell King - ARM Linux
2017-11-28 5:52 ` Masami Hiramatsu
2017-11-28 9:52 ` Russell King - ARM Linux
2017-11-30 2:41 ` Masami Hiramatsu
2017-11-26 12:07 ` Alex Shi
2017-11-27 1:34 ` Masami Hiramatsu
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=c26314ab-90c0-cb04-4c55-ebcf2a7045e4@linaro.org \
--to=alex.shi@linaro.org \
--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.