| 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: <20070125110501.GA25151@elte.hu>
Date: Thu, 25 Jan 2007 12:05:01 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Andrew Morton <akpm@...l.org>
Cc: linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>,
Linus Torvalds <torvalds@...l.org>, Greg KH <gregkh@...e.de>
Subject: [patch] suspend/resume debugging: device filter
Subject: [patch] suspend/resume debugging: device filter
From: Ingo Molnar <mingo@...e.hu>
this patch implements the /sys/power/filter attribute, which takes a
string. If a device's name matches the filter string (exactly), then
that device is excluded from suspend/resume.
this can be helpful in a number of ways when debugging suspend and
resume problems:
- if CONFIG_DISABLE_CONSOLE_SUSPEND is used then the serial
console is still suspended after which point there's no
log output. Doing "echo serial > /sys/power/filter" keeps
the serial port active, so any messages (and crash info)
after that point is displayed.
- if a device is suspected to be the reason of resume failure
then it can be excluded via the filter. That device obviously
wont work, but users can thus help us debug resume problems
in combination with pm_trace, without having to hack the kernel.
(note that you can obvious break suspend/resume via the filter, by
excluding a vital device - so it is only to be used when suspend or
resume is broken to begin with.)
it might be better to do this centrally in sysfs, via a per-device
attribute, to individually enable suspend and resume on a per device
basis, but my sysfs-fu is not strong enough for that now ;-)
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
drivers/base/power/resume.c | 6 ++++
drivers/base/power/suspend.c | 3 +-
include/linux/resume-trace.h | 6 ++++
kernel/power/main.c | 58 +++++++++++++++++++++++++++++++++++++++++++
4 files changed, 72 insertions(+), 1 deletion(-)
Index: linux/drivers/base/power/resume.c
===================================================================
--- linux.orig/drivers/base/power/resume.c
+++ linux/drivers/base/power/resume.c
@@ -24,6 +24,9 @@ int resume_device(struct device * dev)
{
int error = 0;
+ if (power_filter(dev))
+ return 0;
+
TRACE_DEVICE(dev);
TRACE_RESUME(0);
down(&dev->sem);
@@ -52,6 +55,9 @@ static int resume_device_early(struct de
{
int error = 0;
+ if (power_filter(dev))
+ return 0;
+
TRACE_DEVICE(dev);
TRACE_RESUME(0);
if (dev->bus && dev->bus->resume_early) {
Index: linux/drivers/base/power/suspend.c
===================================================================
--- linux.orig/drivers/base/power/suspend.c
+++ linux/drivers/base/power/suspend.c
@@ -10,6 +10,7 @@
#include <linux/device.h>
#include <linux/kallsyms.h>
+#include <linux/resume-trace.h>
#include <linux/pm.h>
#include "../base.h"
#include "power.h"
@@ -78,7 +79,7 @@ int suspend_device(struct device * dev,
suspend_report_result(dev->class->suspend, error);
}
- if (!error && dev->bus && dev->bus->suspend && !dev->power.power_state.event) {
+ if (!error && dev->bus && dev->bus->suspend && !dev->power.power_state.event && !power_filter(dev)) {
dev_dbg(dev, "%s%s\n",
suspend_verb(state.event),
((state.event == PM_EVENT_SUSPEND)
Index: linux/include/linux/resume-trace.h
===================================================================
--- linux.orig/include/linux/resume-trace.h
+++ linux/include/linux/resume-trace.h
@@ -9,6 +9,8 @@ struct device;
extern void set_trace_device(struct device *);
extern void generate_resume_trace(void *tracedata, unsigned int user);
+extern int power_filter(struct device *dev);
+
#define TRACE_DEVICE(dev) set_trace_device(dev)
#define TRACE_RESUME(user) do { \
if (pm_trace_enabled) { \
@@ -28,6 +30,10 @@ extern void generate_resume_trace(void *
#define TRACE_DEVICE(dev) do { } while (0)
#define TRACE_RESUME(dev) do { } while (0)
+static inline int power_filter(struct device *dev)
+{
+ return 0;
+}
#endif
Index: linux/kernel/power/main.c
===================================================================
--- linux.orig/kernel/power/main.c
+++ linux/kernel/power/main.c
@@ -15,6 +15,7 @@
#include <linux/delay.h>
#include <linux/errno.h>
#include <linux/init.h>
+#include <linux/device.h>
#include <linux/pm.h>
#include <linux/console.h>
#include <linux/cpu.h>
@@ -306,9 +307,66 @@ pm_trace_store(struct subsystem * subsys
power_attr(pm_trace);
+/**
+ * filter - exclude drivers from suspend and resume
+ *
+ * show() returns the current filter
+ *
+ * store() accepts a new filter (up to 128 chars long)
+ *
+ * Do "echo serial > /sys/power/filter" to exclude the
+ * serial driver from suspension - this can be useful to
+ * get kernel messages out after the serial console, or to
+ * see which device causes a resume failure.
+ */
+
+#define FILTER_LEN 128
+
+static char power_filter_str[FILTER_LEN+1] = "<none>";
+
+int power_filter(struct device *dev)
+{
+ const char *str = dev_driver_string(dev);
+
+ if (!strcmp(str, power_filter_str)) {
+ printk(KERN_INFO "power filter match for device: %s\n", str);
+ return 1;
+ }
+ return 0;
+}
+
+static ssize_t filter_show(struct subsystem * subsys, char * buf)
+{
+ char *s = buf;
+
+ s += sprintf(s, "%s\n", power_filter_str);
+
+ return (s - buf);
+}
+
+static ssize_t
+filter_store(struct subsystem * subsys, const char * buf, size_t n)
+{
+ unsigned int len;
+
+ strncpy(power_filter_str, buf, FILTER_LEN);
+
+ len = strlen(power_filter_str);
+ /*
+ * Strip off any trailing '\n':
+ */
+ if (len && power_filter_str[len-1] == '\n')
+ power_filter_str[len-1] = 0;
+
+ return len;
+}
+
+power_attr(filter);
+
static struct attribute * g[] = {
&state_attr.attr,
&pm_trace_attr.attr,
+ &filter_attr.attr,
NULL,
};
#else
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists