From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fix infinite stacktrace
Date: Tue, 10 Jul 2018 10:13:39 +0100 [thread overview]
Message-ID: <20180710091338.GA29791@arm.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1807092300520.24277@file01.intranet.prod.int.rdu2.redhat.com>
On Mon, Jul 09, 2018 at 11:04:33PM -0400, Mikulas Patocka wrote:
> On Thu, 28 Jun 2018, Dave Martin wrote:
> > Alternatively, if someone wants to pick up my patch and take it forward,
> > I'm happy to comment.
> >
> > Cheers
> > ---Dave
>
> Or - what about this patch? It doesn't guarantee that infinite loop won't
> happen, but it at least catches the most obvious loop on the same address.
>
>
> From: Mikulas Patocka <mpatocka@redhat.com>
> Subject: [PATCH] arm64: fix infinite stacktrace
>
> I've got this infinite stacktrace when debugging another problem:
> [ 908.795225] INFO: rcu_preempt detected stalls on CPUs/tasks:
> [ 908.796176] 1-...!: (1 GPs behind) idle=952/1/4611686018427387904 softirq=1462/1462 fqs=355
> [ 908.797692] 2-...!: (1 GPs behind) idle=f42/1/4611686018427387904 softirq=1550/1551 fqs=355
> [ 908.799189] (detected by 0, t=2109 jiffies, g=130, c=129, q=235)
> [ 908.800284] Task dump for CPU 1:
> [ 908.800871] kworker/1:1 R running task 0 32 2 0x00000022
> [ 908.802127] Workqueue: writecache-writeabck writecache_writeback [dm_writecache]
> [ 908.820285] Call trace:
> [ 908.824785] __switch_to+0x68/0x90
> [ 908.837661] 0xfffffe00603afd90
> [ 908.844119] 0xfffffe00603afd90
> [ 908.850091] 0xfffffe00603afd90
> [ 908.854285] 0xfffffe00603afd90
> [ 908.863538] 0xfffffe00603afd90
> [ 908.865523] 0xfffffe00603afd90
>
> The machine just locked up and kept on printing the same line over and
> over again. This patch fixes it.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
> Cc: stable at vger.kernel.org
>
> ---
> arch/arm64/kernel/stacktrace.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> Index: linux-2.6/arch/arm64/kernel/stacktrace.c
> ===================================================================
> --- linux-2.6.orig/arch/arm64/kernel/stacktrace.c 2018-07-10 05:01:56.990000000 +0200
> +++ linux-2.6/arch/arm64/kernel/stacktrace.c 2018-07-10 05:02:51.650000000 +0200
> @@ -56,6 +56,9 @@ int notrace unwind_frame(struct task_str
> frame->fp = READ_ONCE_NOCHECK(*(unsigned long *)(fp));
> frame->pc = READ_ONCE_NOCHECK(*(unsigned long *)(fp + 8));
>
> + if (frame->fp == fp)
> + return -EINVAL;
I've already queued your previous patch using '<=' (it's in -next). If you
want to change it, please send patches on top of the arm64 for-next/core
branch.
Will
next prev parent reply other threads:[~2018-07-10 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 18:58 [PATCH] arm64: fix infinite stacktrace Mikulas Patocka
2018-06-15 11:58 ` Mark Rutland
2018-06-27 16:41 ` Will Deacon
2018-06-28 16:49 ` Dave Martin
2018-07-10 3:04 ` Mikulas Patocka
2018-07-10 9:13 ` Will Deacon [this message]
2018-07-10 18:10 ` Mikulas Patocka
2018-07-12 10:39 ` Will Deacon
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=20180710091338.GA29791@arm.com \
--to=will.deacon@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).