| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <X66J0plvSKqFbDIy@kroah.com>
Date: Fri, 13 Nov 2020 14:27:46 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Joseph Jang <josephjang@...gle.com>
Cc: "Rafael J . Wysocki" <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>, Len Brown <len.brown@...el.com>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
jonglin@...gle.com, woodylin@...gle.com, markcheng@...gle.com
Subject: Re: [PATCH v3] power: suspend: Move dpm_watchdog to suspend.c and
enhance it
On Fri, Oct 23, 2020 at 02:04:17PM +0800, Joseph Jang wrote:
> Since dpm_watchdog just cover device power management, we proposed to
> move it to core power suspend.c to cover not only device power management
> hang issues, but also core power management hand issues.
>
> Since dpm_watchdog stands for device pm, we propose to use new name sleep
> timer and new timeout handler to cover more sleep hang issues. The new
> timeout handler will dump disk sleep task at first round timeout and
> trigger kernel panic at second round timeout.
> The default timer for each round is defined in
> CONFIG_PM_SLEEP_TIMER_TIMEOUT.
>
> Signed-off-by: Joseph Jang <josephjang@...gle.com>
It still seems odd you can't use a watchdog for this, as you really have
just implemented the same thing here, but "open coded" the logic.
I'll let Rafael chime in here too, as he knows this area much better
than I as to if this is viable or not.
Some coding comments:
> diff --git a/include/linux/console.h b/include/linux/console.h
> index 0670d3491e0e..5436d8dc600f 100644
> --- a/include/linux/console.h
> +++ b/include/linux/console.h
> @@ -192,6 +192,7 @@ static inline void console_sysfs_notify(void)
> { }
> #endif
> extern bool console_suspend_enabled;
> +extern int console_is_suspended(void);
Why do you care about the console? This feels like it should be
separate and agreed upon by others as to if this is ok to get access to
or not.
>
> /* Suspend and resume console messages over PM events */
> extern void suspend_console(void);
> diff --git a/kernel/power/Kconfig b/kernel/power/Kconfig
> index a7320f07689d..fa021837473b 100644
> --- a/kernel/power/Kconfig
> +++ b/kernel/power/Kconfig
> @@ -207,21 +207,20 @@ config PM_SLEEP_DEBUG
> def_bool y
> depends on PM_DEBUG && PM_SLEEP
>
> -config DPM_WATCHDOG
> - bool "Device suspend/resume watchdog"
> - depends on PM_DEBUG && PSTORE && EXPERT
> +config PM_SLEEP_MONITOR
> + bool "Linux kernel suspend/resume process monitor"
> + depends on PM_SLEEP
> help
> - Sets up a watchdog timer to capture drivers that are
> - locked up attempting to suspend/resume a device.
> - A detected lockup causes system panic with message
> - captured in pstore device for inspection in subsequent
> - boot session.
> -
> -config DPM_WATCHDOG_TIMEOUT
> - int "Watchdog timeout in seconds"
> - range 1 120
> - default 120
> - depends on DPM_WATCHDOG
> + This option will enable sleep timer to prevent device stuck
> + during suspend/resume process. Sleep timeout handler will dump
> + disk sleep task at first round timeout and trigger kernel panic
> + at second round timeout. The timer for each round is defined in
> + CONFIG_PM_SLEEP_TIMER_TIMEOUT.
> +
> +config PM_SLEEP_TIMER_TIMEOUT
> + int "Sleep timer timeout in seconds"
> + range 30 120
> + depends on PM_SLEEP_MONITOR
>
> config PM_TRACE
> bool
> diff --git a/kernel/power/suspend.c b/kernel/power/suspend.c
> index 8b1bb5ee7e5d..0272494e0d0e 100644
> --- a/kernel/power/suspend.c
> +++ b/kernel/power/suspend.c
> @@ -32,6 +32,7 @@
> #include <linux/moduleparam.h>
>
> #include "power.h"
> +#include "suspend_timer.h"
>
> const char * const pm_labels[] = {
> [PM_SUSPEND_TO_IDLE] = "freeze",
> @@ -61,6 +62,8 @@ static DECLARE_SWAIT_QUEUE_HEAD(s2idle_wait_head);
> enum s2idle_states __read_mostly s2idle_state;
> static DEFINE_RAW_SPINLOCK(s2idle_lock);
>
> +DECLARE_SLEEP_TIMER(st);
Why is this not static? "st" is a very bad name for a global symbol in
the kernel namespace :(
> --- /dev/null
> +++ b/kernel/power/suspend_timer.h
> @@ -0,0 +1,90 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#ifndef _LINUX_SLEEP_TIMER_H
> +#define _LINUX_SLEEP_TIMER_H
> +
> +#include <linux/sched/debug.h>
> +
> +#ifdef CONFIG_PM_SLEEP_MONITOR
> +struct sleep_timer {
> + struct task_struct *tsk;
> + struct timer_list timer;
> +};
> +
> +#define DECLARE_SLEEP_TIMER(st) \
> + struct sleep_timer st
> +
> +/**
> + * init_sleep_timer - Initialize sleep timer.
> + * @st: Sleep timer to initialize.
> + * @func: Sleep timer timeout handler.
> + */
> +static void init_sleep_timer(struct sleep_timer *st, void (*func))
> +{
> + struct timer_list *timer = &st->timer;
> +
> + timer_setup(timer, func, 0);
> +}
> +
> +/**
> + * start_sleep_timer - Enable sleep timer to monitor suspend thread.
> + * @st: Sleep timer to enable.
> + */
> +static void start_sleep_timer(struct sleep_timer *st)
> +{
> + struct timer_list *timer = &st->timer;
> +
> + st->tsk = current;
> +
> + /* use same timeout value for both suspend and resume */
> + timer->expires = jiffies + HZ * CONFIG_PM_SLEEP_TIMER_TIMEOUT;
> + add_timer(timer);
> +}
> +
> +/**
> + * stop_sleep_timer - Disable sleep timer.
> + * @st: sleep timer to disable.
> + */
> +static void stop_sleep_timer(struct sleep_timer *st)
> +{
> + struct timer_list *timer = &st->timer;
> +
> + del_timer_sync(timer);
> +}
> +
> +/**
> + * sleep_timeout_handler - sleep timer timeout handler.
> + * @t: The timer list that sleep timer depends on.
> + *
> + * Called when suspend thread has timeout suspending or resuming.
> + * Dump all uninterruptible tasks' call stack and call panic() to
> + * reboot system in second round timeout.
> + */
> +static void sleep_timeout_handler(struct timer_list *t)
> +{
> + struct sleep_timer *st = from_timer(st, t, timer);
> + static int timeout_count;
> +
> + pr_info("Sleep timeout (timer is %d seconds)\n",
> + (CONFIG_PM_SLEEP_TIMER_TIMEOUT));
> + show_stack(st->tsk, NULL, KERN_EMERG);
> + show_state_filter(TASK_UNINTERRUPTIBLE);
> +
> + if (timeout_count < 1) {
> + timeout_count++;
> + start_sleep_timer(st);
> + return;
> + }
> +
> + if (console_is_suspended())
> + resume_console();
> +
> + panic("Sleep timeout and panic\n");
> +}
You have a lot of logic in a .h file, that should all be in a .c file.
Just put the function prototypes in here and put the real logic in a .c
file, and only link that in if the config option is enabled. As it is,
this isn't ok no matter what.
> +#else
> +#define DECLARE_SLEEP_TIMER(st)
> +#define init_sleep_timer(x, y)
> +#define start_sleep_timer(x)
> +#define stop_sleep_timer(x)
Use inline functions so you get proper type checking, not #define.
> +#endif
> +
> +#endif /* _LINUX_SLEEP_TIMER_H */
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 9b75f6bfc333..488cbc9abaaf 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2259,6 +2259,11 @@ module_param_named(console_suspend, console_suspend_enabled,
> MODULE_PARM_DESC(console_suspend, "suspend console during suspend"
> " and hibernate operations");
>
> +int console_is_suspended(void)
> +{
> + return console_suspended;
> +}
Again, I don't think this is ok. What happens if this changes _right_
after you check it? Why does it matter?
thanks,
greg k-h
Powered by blists - more mailing lists