On 26/02/2023 02:44, Andrew Morton wrote: > On Fri, 10 Feb 2023 17:35:10 -0300 "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxx> wrote: > [...] >> Notice that while at it, I got rid of the "crash_kexec_post_notifiers" >> local copy in panic(). This was introduced by commit b26e27ddfd2a >> ("kexec: use core_param for crash_kexec_post_notifiers boot option"), >> but it is not clear from comments or commit message why this local copy >> is required. >> >> My understanding is that it's a mechanism to prevent some concurrency, >> in case some other CPU modify this variable while panic() is running. >> I find it very unlikely, hence I removed it - but if people consider >> this copy needed, I can respin this patch and keep it, even providing a >> comment about that, in order to be explict about its need. > > Only two sites change crash_kexec_post_notifiers, in > arch/powerpc/kernel/fadump.c and drivers/hv/hv_common.c. Yes, it's > very unlikely that this will be altered while panic() is running and > the consequences will be slight anyway. > > But formally, we shouldn't do this, especially in a -stable > backportable patch. So please, let's have the minimal bugfix for now > and we can look at removing that local at a later time? > Thanks Andrew, I agree with you! I just sent a V5 with the bugfix alone, not changing this local/global variable behavior. Cheers, Guilherme _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec