From: Laurent Dufour <ldufour@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/watchdog: Fix wd_smp_last_reset_tb reporting
Date: Thu, 25 Nov 2021 18:21:36 +0100 [thread overview]
Message-ID: <f8d08f56-29b7-5a17-9e64-5ac36731b9df@linux.ibm.com> (raw)
In-Reply-To: <20211125103346.1188958-1-npiggin@gmail.com>
On 25/11/2021, 11:33:46, Nicholas Piggin wrote:
> wd_smp_last_reset_tb now gets reset by watchdog_smp_panic() as part of
> marking CPUs stuck and removing them from the pending mask before it
> begins any printing. This causes last reset times reported to be off.
>
> Fix this by reading it into a local variable before it gets reset.
>
> Fixes: 76521c4b0291 ("powerpc/watchdog: Avoid holding wd_smp_lock over printk and smp_send_nmi_ipi")
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
>
> This is the delta for patches 1-4 between v3 and v4 of the series which
> is the result of fixing the bug in patch 3. Sending because v3 got
> merged into powerpc next
What about the 5th patch in the v4 series titled "[PATCH v4 5/5]
powerpc/watchdog: help remote CPUs to flush NMI printk output"?
> Thanks,
> Nick
>
> arch/powerpc/kernel/watchdog.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c
> index b6533539386b..23745af38d62 100644
> --- a/arch/powerpc/kernel/watchdog.c
> +++ b/arch/powerpc/kernel/watchdog.c
> @@ -179,13 +179,14 @@ static void watchdog_smp_panic(int cpu)
> {
> static cpumask_t wd_smp_cpus_ipi; // protected by reporting
> unsigned long flags;
> - u64 tb;
> + u64 tb, last_reset;
> int c;
>
> wd_smp_lock(&flags);
> /* Double check some things under lock */
> tb = get_tb();
> - if ((s64)(tb - wd_smp_last_reset_tb) < (s64)wd_smp_panic_timeout_tb)
> + last_reset = wd_smp_last_reset_tb;
> + if ((s64)(tb - last_reset) < (s64)wd_smp_panic_timeout_tb)
> goto out;
> if (cpumask_test_cpu(cpu, &wd_smp_cpus_pending))
> goto out;
> @@ -210,8 +211,7 @@ static void watchdog_smp_panic(int cpu)
> pr_emerg("CPU %d detected hard LOCKUP on other CPUs %*pbl\n",
> cpu, cpumask_pr_args(&wd_smp_cpus_ipi));
> pr_emerg("CPU %d TB:%lld, last SMP heartbeat TB:%lld (%lldms ago)\n",
> - cpu, tb, wd_smp_last_reset_tb,
> - tb_to_ns(tb - wd_smp_last_reset_tb) / 1000000);
> + cpu, tb, last_reset, tb_to_ns(tb - last_reset) / 1000000);
>
> if (!sysctl_hardlockup_all_cpu_backtrace) {
> /*
>
next prev parent reply other threads:[~2021-11-25 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 10:33 [PATCH] powerpc/watchdog: Fix wd_smp_last_reset_tb reporting Nicholas Piggin
2021-11-25 11:00 ` Michael Ellerman
2021-11-25 17:21 ` Laurent Dufour [this message]
2021-11-26 0:50 ` Nicholas Piggin
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=f8d08f56-29b7-5a17-9e64-5ac36731b9df@linux.ibm.com \
--to=ldufour@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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).