From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Lvqiang <Lvqiang.Huang@unisoc.com>
Cc: f.fainelli@gmail.com, anshuman.khandual@arm.com,
dave.hansen@linux.intel.com, linux-kernel@vger.kernel.org,
ebiederm@xmission.com, akpm@linux-foundation.org,
will@kernel.org, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: check __ex_table in do_bad()
Date: Thu, 7 Nov 2019 09:24:04 +0000 [thread overview]
Message-ID: <20191107092404.GV25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <1573112713-10115-1-git-send-email-Lvqiang.Huang@unisoc.com>
On Thu, Nov 07, 2019 at 03:45:13PM +0800, Lvqiang wrote:
>
> We got many crashs in for_each_frame+0x18 arch/arm/lib/backtrace.S
> 1003: ldr r2, [sv_pc, #-4]
>
> The backtrace is
> dump_backtrace
> show_stack
> sched_show_task
> show_state_filter
> sysrq_handle_showstate_blocked
> __handle_sysrq
> write_sysrq_trigger
> proc_reg_write
> __vfs_write
> vfs_write
> sys_write
>
> Related Kernel config
> CONFIG_CPU_SW_DOMAIN_PAN=y
> # CONFIG_ARM_UNWIND is not set
> CONFIG_FRAME_POINTER=y
>
> The task A was dumping the stack of an UN task B. However, the task B
What is "an UN task B"?
> scheduled to run on another CPU, which cause it stack content changed.
> Then, task A may hit a page domain fault and die().
> [520.661314] Unhandled fault: page domain fault (0x01b) at 0x32848c02
So, the backtrace code is trying to access userspace. It isn't supposed
to be accessing userspace - there are no guarantees that userspace will
be using frame pointers. That is the bug.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Lvqiang <Lvqiang.Huang@unisoc.com>
Cc: ebiederm@xmission.com, dave.hansen@linux.intel.com,
anshuman.khandual@arm.com, akpm@linux-foundation.org,
f.fainelli@gmail.com, will@kernel.org, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: check __ex_table in do_bad()
Date: Thu, 7 Nov 2019 09:24:04 +0000 [thread overview]
Message-ID: <20191107092404.GV25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <1573112713-10115-1-git-send-email-Lvqiang.Huang@unisoc.com>
On Thu, Nov 07, 2019 at 03:45:13PM +0800, Lvqiang wrote:
>
> We got many crashs in for_each_frame+0x18 arch/arm/lib/backtrace.S
> 1003: ldr r2, [sv_pc, #-4]
>
> The backtrace is
> dump_backtrace
> show_stack
> sched_show_task
> show_state_filter
> sysrq_handle_showstate_blocked
> __handle_sysrq
> write_sysrq_trigger
> proc_reg_write
> __vfs_write
> vfs_write
> sys_write
>
> Related Kernel config
> CONFIG_CPU_SW_DOMAIN_PAN=y
> # CONFIG_ARM_UNWIND is not set
> CONFIG_FRAME_POINTER=y
>
> The task A was dumping the stack of an UN task B. However, the task B
What is "an UN task B"?
> scheduled to run on another CPU, which cause it stack content changed.
> Then, task A may hit a page domain fault and die().
> [520.661314] Unhandled fault: page domain fault (0x01b) at 0x32848c02
So, the backtrace code is trying to access userspace. It isn't supposed
to be accessing userspace - there are no guarantees that userspace will
be using frame pointers. That is the bug.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-11-07 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 7:45 [PATCH] ARM: check __ex_table in do_bad() Lvqiang
2019-11-07 7:45 ` Lvqiang
2019-11-07 9:24 ` Russell King - ARM Linux admin [this message]
2019-11-07 9:24 ` Russell King - ARM Linux admin
2019-11-07 15:30 ` 黄吕强 (Lvqiang Huang)
2019-11-07 15:30 ` 黄吕强 (Lvqiang Huang)
2019-11-07 17:22 ` 黄吕强 (Lvqiang Huang)
2019-11-07 17:22 ` 黄吕强 (Lvqiang Huang)
2019-11-08 2:16 ` 黄吕强 (Lvqiang Huang)
2019-11-08 2:16 ` 黄吕强 (Lvqiang Huang)
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=20191107092404.GV25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Lvqiang.Huang@unisoc.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.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.