2019-06-20 23:28:46 +07:00
|
|
|
// SPDX-License-Identifier: GPL-2.0+
|
2005-04-17 05:20:36 +07:00
|
|
|
/*
|
2012-02-29 05:48:11 +07:00
|
|
|
* SoftDog: A Software Watchdog Device
|
2005-04-17 05:20:36 +07:00
|
|
|
*
|
2009-03-18 15:35:09 +07:00
|
|
|
* (c) Copyright 1996 Alan Cox <alan@lxorguk.ukuu.org.uk>,
|
|
|
|
* All Rights Reserved.
|
2005-04-17 05:20:36 +07:00
|
|
|
*
|
|
|
|
* Neither Alan Cox nor CymruNet Ltd. admit liability nor provide
|
|
|
|
* warranty for any of this software. This material is provided
|
|
|
|
* "AS-IS" and at no charge.
|
|
|
|
*
|
|
|
|
* (c) Copyright 1995 Alan Cox <alan@lxorguk.ukuu.org.uk>
|
|
|
|
*
|
|
|
|
* Software only watchdog driver. Unlike its big brother the WDT501P
|
|
|
|
* driver this won't always recover a failed machine.
|
|
|
|
*/
|
|
|
|
|
2012-02-16 06:06:19 +07:00
|
|
|
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
|
|
|
|
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
#include <linux/hrtimer.h>
|
2016-05-25 13:37:47 +07:00
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/kernel.h>
|
2020-07-08 15:32:19 +07:00
|
|
|
#include <linux/kthread.h>
|
2005-04-17 05:20:36 +07:00
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/moduleparam.h>
|
2016-05-25 13:37:47 +07:00
|
|
|
#include <linux/reboot.h>
|
|
|
|
#include <linux/types.h>
|
2005-04-17 05:20:36 +07:00
|
|
|
#include <linux/watchdog.h>
|
2020-07-08 15:32:19 +07:00
|
|
|
#include <linux/workqueue.h>
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
#define TIMER_MARGIN 60 /* Default is 60 seconds */
|
2012-02-29 05:48:11 +07:00
|
|
|
static unsigned int soft_margin = TIMER_MARGIN; /* in seconds */
|
|
|
|
module_param(soft_margin, uint, 0);
|
2008-05-19 20:09:06 +07:00
|
|
|
MODULE_PARM_DESC(soft_margin,
|
|
|
|
"Watchdog soft_margin in seconds. (0 < soft_margin < 65536, default="
|
|
|
|
__MODULE_STRING(TIMER_MARGIN) ")");
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2012-03-05 22:51:11 +07:00
|
|
|
static bool nowayout = WATCHDOG_NOWAYOUT;
|
|
|
|
module_param(nowayout, bool, 0);
|
2008-05-19 20:09:06 +07:00
|
|
|
MODULE_PARM_DESC(nowayout,
|
|
|
|
"Watchdog cannot be stopped once started (default="
|
|
|
|
__MODULE_STRING(WATCHDOG_NOWAYOUT) ")");
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2014-02-27 12:41:42 +07:00
|
|
|
static int soft_noboot;
|
2005-04-17 05:20:36 +07:00
|
|
|
module_param(soft_noboot, int, 0);
|
2009-04-15 03:20:07 +07:00
|
|
|
MODULE_PARM_DESC(soft_noboot,
|
2012-02-29 05:48:11 +07:00
|
|
|
"Softdog action, set to 1 to ignore reboots, 0 to reboot (default=0)");
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2011-03-29 04:29:19 +07:00
|
|
|
static int soft_panic;
|
|
|
|
module_param(soft_panic, int, 0);
|
|
|
|
MODULE_PARM_DESC(soft_panic,
|
|
|
|
"Softdog action, set to 1 to panic, 0 to reboot (default=0)");
|
|
|
|
|
2020-07-08 15:32:19 +07:00
|
|
|
static char *soft_reboot_cmd;
|
|
|
|
module_param(soft_reboot_cmd, charp, 0000);
|
|
|
|
MODULE_PARM_DESC(soft_reboot_cmd,
|
|
|
|
"Set reboot command. Emergency reboot takes place if unset");
|
|
|
|
|
|
|
|
static bool soft_active_on_boot;
|
|
|
|
module_param(soft_active_on_boot, bool, 0000);
|
|
|
|
MODULE_PARM_DESC(soft_active_on_boot,
|
|
|
|
"Set to true to active Softdog on boot (default=false)");
|
|
|
|
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
static struct hrtimer softdog_ticktock;
|
|
|
|
static struct hrtimer softdog_preticktock;
|
|
|
|
|
2020-07-08 15:32:19 +07:00
|
|
|
static int reboot_kthread_fn(void *data)
|
|
|
|
{
|
|
|
|
kernel_restart(soft_reboot_cmd);
|
|
|
|
return -EPERM; /* Should not reach here */
|
|
|
|
}
|
|
|
|
|
|
|
|
static void reboot_work_fn(struct work_struct *unused)
|
|
|
|
{
|
|
|
|
kthread_run(reboot_kthread_fn, NULL, "softdog_reboot");
|
|
|
|
}
|
|
|
|
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
static enum hrtimer_restart softdog_fire(struct hrtimer *timer)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2020-07-08 15:32:19 +07:00
|
|
|
static bool soft_reboot_fired;
|
|
|
|
|
2015-12-17 20:30:02 +07:00
|
|
|
module_put(THIS_MODULE);
|
2016-05-25 13:37:49 +07:00
|
|
|
if (soft_noboot) {
|
2012-02-16 06:06:19 +07:00
|
|
|
pr_crit("Triggered - Reboot ignored\n");
|
2016-05-25 13:37:49 +07:00
|
|
|
} else if (soft_panic) {
|
2012-02-16 06:06:19 +07:00
|
|
|
pr_crit("Initiating panic\n");
|
|
|
|
panic("Software Watchdog Timer expired");
|
2011-03-29 04:29:19 +07:00
|
|
|
} else {
|
2012-02-16 06:06:19 +07:00
|
|
|
pr_crit("Initiating system reboot\n");
|
2020-07-08 15:32:19 +07:00
|
|
|
if (!soft_reboot_fired && soft_reboot_cmd != NULL) {
|
|
|
|
static DECLARE_WORK(reboot_work, reboot_work_fn);
|
|
|
|
/*
|
|
|
|
* The 'kernel_restart' is a 'might-sleep' operation.
|
|
|
|
* Also, executing it in system-wide workqueues blocks
|
|
|
|
* any driver from using the same workqueue in its
|
|
|
|
* shutdown callback function. Thus, we should execute
|
|
|
|
* the 'kernel_restart' in a standalone kernel thread.
|
|
|
|
* But since starting a kernel thread is also a
|
|
|
|
* 'might-sleep' operation, so the 'reboot_work' is
|
|
|
|
* required as a launcher of the kernel thread.
|
|
|
|
*
|
|
|
|
* After request the reboot, restart the timer to
|
|
|
|
* schedule an 'emergency_restart' reboot after
|
|
|
|
* 'TIMER_MARGIN' seconds. It's because if the softdog
|
|
|
|
* hangs, it might be because of scheduling issues. And
|
|
|
|
* if that is the case, both 'schedule_work' and
|
|
|
|
* 'kernel_restart' may possibly be malfunctional at the
|
|
|
|
* same time.
|
|
|
|
*/
|
|
|
|
soft_reboot_fired = true;
|
|
|
|
schedule_work(&reboot_work);
|
|
|
|
hrtimer_add_expires_ns(timer,
|
|
|
|
(u64)TIMER_MARGIN * NSEC_PER_SEC);
|
|
|
|
|
|
|
|
return HRTIMER_RESTART;
|
|
|
|
}
|
2005-07-27 11:41:38 +07:00
|
|
|
emergency_restart();
|
2012-02-16 06:06:19 +07:00
|
|
|
pr_crit("Reboot didn't ?????\n");
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
return HRTIMER_NORESTART;
|
|
|
|
}
|
2016-05-25 13:37:46 +07:00
|
|
|
|
2016-10-07 19:41:38 +07:00
|
|
|
static struct watchdog_device softdog_dev;
|
|
|
|
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
static enum hrtimer_restart softdog_pretimeout(struct hrtimer *timer)
|
2016-10-07 19:41:38 +07:00
|
|
|
{
|
|
|
|
watchdog_notify_pretimeout(&softdog_dev);
|
|
|
|
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
return HRTIMER_NORESTART;
|
|
|
|
}
|
2016-10-07 19:41:38 +07:00
|
|
|
|
2012-02-29 05:48:11 +07:00
|
|
|
static int softdog_ping(struct watchdog_device *w)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
if (!hrtimer_active(&softdog_ticktock))
|
2015-12-17 20:30:02 +07:00
|
|
|
__module_get(THIS_MODULE);
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
hrtimer_start(&softdog_ticktock, ktime_set(w->timeout, 0),
|
|
|
|
HRTIMER_MODE_REL);
|
2016-10-07 19:41:38 +07:00
|
|
|
|
2017-02-07 21:03:29 +07:00
|
|
|
if (IS_ENABLED(CONFIG_SOFT_WATCHDOG_PRETIMEOUT)) {
|
|
|
|
if (w->pretimeout)
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
hrtimer_start(&softdog_preticktock,
|
|
|
|
ktime_set(w->timeout - w->pretimeout, 0),
|
|
|
|
HRTIMER_MODE_REL);
|
2017-02-07 21:03:29 +07:00
|
|
|
else
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
hrtimer_cancel(&softdog_preticktock);
|
2017-02-07 21:03:29 +07:00
|
|
|
}
|
2016-10-07 19:41:38 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-02-29 05:48:11 +07:00
|
|
|
static int softdog_stop(struct watchdog_device *w)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
if (hrtimer_cancel(&softdog_ticktock))
|
2015-12-17 20:30:02 +07:00
|
|
|
module_put(THIS_MODULE);
|
|
|
|
|
2017-02-07 21:03:29 +07:00
|
|
|
if (IS_ENABLED(CONFIG_SOFT_WATCHDOG_PRETIMEOUT))
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
hrtimer_cancel(&softdog_preticktock);
|
2016-10-07 19:41:38 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-02-29 05:48:11 +07:00
|
|
|
static struct watchdog_info softdog_info = {
|
|
|
|
.identity = "Software Watchdog",
|
2017-02-07 21:03:29 +07:00
|
|
|
.options = WDIOF_SETTIMEOUT | WDIOF_KEEPALIVEPING | WDIOF_MAGICCLOSE,
|
2005-04-17 05:20:36 +07:00
|
|
|
};
|
|
|
|
|
2016-09-02 00:35:26 +07:00
|
|
|
static const struct watchdog_ops softdog_ops = {
|
2012-02-29 05:48:11 +07:00
|
|
|
.owner = THIS_MODULE,
|
|
|
|
.start = softdog_ping,
|
|
|
|
.stop = softdog_stop,
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct watchdog_device softdog_dev = {
|
|
|
|
.info = &softdog_info,
|
|
|
|
.ops = &softdog_ops,
|
|
|
|
.min_timeout = 1,
|
2016-05-25 13:37:44 +07:00
|
|
|
.max_timeout = 65535,
|
|
|
|
.timeout = TIMER_MARGIN,
|
2005-04-17 05:20:36 +07:00
|
|
|
};
|
|
|
|
|
2016-05-25 13:37:45 +07:00
|
|
|
static int __init softdog_init(void)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
2016-05-25 13:37:44 +07:00
|
|
|
watchdog_init_timeout(&softdog_dev, soft_margin, NULL);
|
2012-02-29 05:48:11 +07:00
|
|
|
watchdog_set_nowayout(&softdog_dev, nowayout);
|
2015-11-21 04:54:55 +07:00
|
|
|
watchdog_stop_on_reboot(&softdog_dev);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
hrtimer_init(&softdog_ticktock, CLOCK_MONOTONIC, HRTIMER_MODE_REL);
|
|
|
|
softdog_ticktock.function = softdog_fire;
|
|
|
|
|
|
|
|
if (IS_ENABLED(CONFIG_SOFT_WATCHDOG_PRETIMEOUT)) {
|
2017-02-07 21:03:29 +07:00
|
|
|
softdog_info.options |= WDIOF_PRETIMEOUT;
|
watchdog: softdog: fire watchdog even if softirqs do not get to run
Checking for timer expiration is done from the softirq TIMER_SOFTIRQ.
Since commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job"),
pending softirqs are no longer always handled immediately, instead,
if there are pending softirqs, and ksoftirqd is in state TASK_RUNNING,
the handling of the softirqs are deferred, and are instead supposed
to be handled by ksoftirqd, when ksoftirqd gets scheduled.
If a user space process with a real-time policy starts to misbehave
by never relinquishing the CPU while ksoftirqd is in state TASK_RUNNING,
what will happen is that all softirqs will get deferred, while ksoftirqd,
which is supposed to handle the deferred softirqs, will never get to run.
To make sure that the watchdog is able to fire even when we do not get
to run softirqs, replace the timers with hrtimers.
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
2017-02-27 19:49:09 +07:00
|
|
|
hrtimer_init(&softdog_preticktock, CLOCK_MONOTONIC,
|
|
|
|
HRTIMER_MODE_REL);
|
|
|
|
softdog_preticktock.function = softdog_pretimeout;
|
|
|
|
}
|
2017-02-07 21:03:29 +07:00
|
|
|
|
2020-07-08 15:32:19 +07:00
|
|
|
if (soft_active_on_boot)
|
|
|
|
softdog_ping(&softdog_dev);
|
|
|
|
|
2012-02-29 05:48:11 +07:00
|
|
|
ret = watchdog_register_device(&softdog_dev);
|
2015-11-21 04:54:55 +07:00
|
|
|
if (ret)
|
2005-04-17 05:20:36 +07:00
|
|
|
return ret;
|
|
|
|
|
2016-05-25 13:37:44 +07:00
|
|
|
pr_info("initialized. soft_noboot=%d soft_margin=%d sec soft_panic=%d (nowayout=%d)\n",
|
|
|
|
soft_noboot, softdog_dev.timeout, soft_panic, nowayout);
|
2020-07-08 15:32:19 +07:00
|
|
|
pr_info(" soft_reboot_cmd=%s soft_active_on_boot=%d\n",
|
|
|
|
soft_reboot_cmd ?: "<not set>", soft_active_on_boot);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2016-05-25 13:37:45 +07:00
|
|
|
module_init(softdog_init);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2016-05-25 13:37:45 +07:00
|
|
|
static void __exit softdog_exit(void)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2012-02-29 05:48:11 +07:00
|
|
|
watchdog_unregister_device(&softdog_dev);
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2016-05-25 13:37:45 +07:00
|
|
|
module_exit(softdog_exit);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
MODULE_AUTHOR("Alan Cox");
|
|
|
|
MODULE_DESCRIPTION("Software Watchdog Device Driver");
|
|
|
|
MODULE_LICENSE("GPL");
|