linux-kernel - common watchdog interface: handling of suspend/resume

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a0802152054l6d6a9b0aq8226c168006834b8@mail.gmail.com>
Date:	Fri, 15 Feb 2008 23:54:51 -0500
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"Wim Van Sebroeck" <wim@...ana.be>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: common watchdog interface: handling of suspend/resume

i'm not sure if it is possible to integrate this into the common code
(be great if we could), but we should codify the expected behavior for
the suspend/resume functions.  from looking at the 8 that implement
the pm functions, they seem to all do:
suspend(): turn off the watchdog
resume(): turn on the watchdog if it was running

some other issues raised:
 - this device should not be able to be selective suspended ... in
other words, you only want to "suspend" the watchdog if the whole
system is going to be suspend
 - should the nowayout option be checked at all ?
-mike
--
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/