All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
To: Ryo Takakura <ryotkkr98@gmail.com>
Cc: akpm@linux-foundation.org, bhe@redhat.com, decui@microsoft.com,
	gregkh@linuxfoundation.org, haiyangz@microsoft.com,
	jani.nikula@intel.com, jfalempe@redhat.com,
	joel.granados@kernel.org, john.ogness@linutronix.de,
	linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
	pmladek@suse.com, takakura@valinux.co.jp, wei.liu@kernel.org
Subject: Re: [PATCH RFC] panic: call panic handlers before panic_other_cpus_shutdown()
Date: Fri, 21 Feb 2025 16:23:07 -0500	[thread overview]
Message-ID: <Z7juu2YMiVfYm7ZM@hm-sls2> (raw)
In-Reply-To: <20250221022328.47078-1-ryotkkr98@gmail.com>

Hey Ryo,

On Fri, Feb 21, 2025 at 11:23:28AM +0900, Ryo Takakura wrote:
> Hi Hamza!
> 
> On Thu, 20 Feb 2025 17:53:00 -0500, Hamza Mahfooz wrote:
> >Since, the panic handlers may require certain cpus to be online to panic
> >gracefully, we should call them before turning off SMP. Without this
> >re-ordering, on Hyper-V hv_panic_vmbus_unload() times out, because the
> >vmbus channel is bound to VMBUS_CONNECT_CPU and unless the crashing cpu
> >is the same as VMBUS_CONNECT_CPU, VMBUS_CONNECT_CPU will be offlined by
> >crash_smp_send_stop() before the vmbus channel can be deconstructed.
> >
> >Signed-off-by: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
> >---
> > kernel/panic.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> >diff --git a/kernel/panic.c b/kernel/panic.c
> >index fbc59b3b64d0..9712a46dfe27 100644
> >--- a/kernel/panic.c
> >+++ b/kernel/panic.c
> >@@ -372,8 +372,6 @@ void panic(const char *fmt, ...)
> > 	if (!_crash_kexec_post_notifiers)
> > 		__crash_kexec(NULL);
> > 
> >-	panic_other_cpus_shutdown(_crash_kexec_post_notifiers);
> >-
> > 	printk_legacy_allow_panic_sync();
> 
> I think printk_legacy_allow_panic_sync() is placed after 
> panic_other_cpus_shutdown() so that it flushes the stored 
> cpus backtraces as described [0].
> 
> > 	/*
> >@@ -382,6 +380,8 @@ void panic(const char *fmt, ...)
> > 	 */
> > 	atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
> > 
> >+	panic_other_cpus_shutdown(_crash_kexec_post_notifiers);
> >+
> 
> So maybe panic_other_cpus_shutdown() should be palced after 
> atomic_notifier_call_chain() along with printk_legacy_allow_panic_sync()
> like below?
> 
> ----- BEGIN -----
> diff --git a/kernel/panic.c b/kernel/panic.c
> index d8635d5cecb2..7ac40e85ee27 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -372,16 +372,16 @@ void panic(const char *fmt, ...)
>         if (!_crash_kexec_post_notifiers)
>                 __crash_kexec(NULL);
> 
> -       panic_other_cpus_shutdown(_crash_kexec_post_notifiers);
> -
> -       printk_legacy_allow_panic_sync();
> -
>         /*
>          * Run any panic handlers, including those that might need to
>          * add information to the kmsg dump output.
>          */
>         atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
> 
> +       panic_other_cpus_shutdown(_crash_kexec_post_notifiers);
> +
> +       printk_legacy_allow_panic_sync();
> +
>         panic_print_sys_info(false);
> 
>         kmsg_dump_desc(KMSG_DUMP_PANIC, buf);
> ----- END -----

Ya, that looks fine to me, that's actually how I had it initally, but I
wasn't sure if it had to go before the panic handlers. So, I erred on
the side of caution.

BR,
Hamza

> 
> Sincerely,
> Ryo Takakura
> 
> [0] https://lore.kernel.org/all/20240820063001.36405-30-john.ogness@linutronix.de/

  reply	other threads:[~2025-02-21 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 22:53 [PATCH RFC] panic: call panic handlers before panic_other_cpus_shutdown() Hamza Mahfooz
2025-02-21  2:23 ` Ryo Takakura
2025-02-21 21:23   ` Hamza Mahfooz [this message]
2025-02-22  5:44     ` Ryo Takakura
2025-02-26 15:49       ` Petr Mladek
2025-03-02  6:36         ` Ryo Takakura

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=Z7juu2YMiVfYm7ZM@hm-sls2 \
    --to=hamzamahfooz@linux.microsoft.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=decui@microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=jani.nikula@intel.com \
    --cc=jfalempe@redhat.com \
    --cc=joel.granados@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=ryotkkr98@gmail.com \
    --cc=takakura@valinux.co.jp \
    --cc=wei.liu@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.