On Tue, 14 Jan 2014 16:23:23 +0800 Dave Young <dyoung@xxxxxxxxxx> wrote: > In kdump kernel watchdog could interrupt vmcore capturing because we > have no way to disable/stop it while crashing happens. Lots of watchdogs cannot be stopped. > Add a module parameter stop_before_register so watchdog can be stopped > before register in driver loading path. Thus we can try to load the > watchdog driver as early as possible in kdump kernel to ensure vmcore > capturing. If you want to kdump then don't start the watchdog. The goal of the watchdog is to make sure the system never gets stuck. Adding conditions and special cases simply increases the odds of something bad not triggering the watchdog. If you have a system that can stop the watchdog then providing no way out is not set you can open it and stop it. I don't see the need for any kernel change here - if it can't be stopped you lost - if "nowayout" is set then by design you lost - if it can be stopped, you can open and stop it Now whether in the !nowayout case the watchdog core should catch whatever hooks/notifiers are available and stop any watchdogs it can on a kexec/kdump is a more interesting question and probably needs to default to not doing so but with the option to force otherwise for debugging work. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
