Hello Eric and Daniel, (2015/07/14 5:26), dwalker@xxxxxxxxxx wrote: > On Fri, Jul 10, 2015 at 08:41:28AM -0500, Eric W. Biederman wrote: >> Hidehiro Kawai <hidehiro.kawai.ez@xxxxxxxxxxx> writes: >> >>> You can call panic notifiers and kmsg dumpers before kdump by >>> specifying "crash_kexec_post_notifiers" as a boot parameter. >>> However, it doesn't make sense if kdump is not available. In that >>> case, disable "crash_kexec_post_notifiers" boot parameter so that >>> you can't change the value of the parameter. >> >> Nacked-by: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx> >> >> You are confusing kexec on panic and CONFIG_CRASH_DUMP >> which is about the tools for reading the state of the previous kernel. You are right. I mistook the meaning of CONFIG_CRASH_DUMP. > I think it would make sense if he just replaced "kdump" with "kexec". If a user specified crash_kexec_post_notifiers option with kexec being totally disabled, it just disables notifier and kmsg dumper calls (please see PATCH 3/3). So as Daniel said, I also think it makes sense to hide crash_kexec_post_notifiers option if kexec is disabled. Regards, -- Hidehiro Kawai Hitachi, Ltd. Research & Development Group -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
