Hi Guilherme, On 12/22/21 at 09:34am, Guilherme G. Piccoli wrote: > On 22/12/2021 08:45, Dave Young wrote: > > Hi Guilherme, > > > > Thanks for you patch. Could you add kexec list for any following up > > patches? This could change kdump behavior so let's see if any comments > > from kexec list. > > > > Kudos for the lore+lei tool so that I can catch this by seeing this > > coming into Andrews tree :) > > Hi Dave, I'm really sorry for not adding the kexec list, I forgot. But I > will do next time for sure, my apologies. And thanks for taking a look > after you noticed that on lore, I appreciate your feedback! Thanks! > > > [...] > > People may enable kdump crashkernel and panic_print together but > > they are not aware the extra panic print could cause kdump not reliable > > (in theory). So at least some words in kernel-parameters.txt would > > help. > > > > That makes sense, I'll improve that in a follow-up patch, how about > that? Indeed it's a good idea to let people be sure that panic_print > might affect kdump reliability, although I consider the risk to be > pretty low. And I'll loop the kexec list for sure! If only the doc update, I think it is fine to be another follup-up patch. About your 1st option in patch log, there is crash_kexec_post_notifiers kernel param which can be used to switch on panic notifiers before kdump bootup. Another way probably you can try to move panic print to be panic notifier. Have this been discussed before? > > Cheers, > > > Guilherme Thanks Dave
