linux-kernel - watchdog behaviour on close? (watchdog-api.txt)

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <c166aa9f0712180941o765cba7fxf31705560a51a06c@mail.gmail.com>
Date:	Tue, 18 Dec 2007 11:41:05 -0600
From:	"Andrew Dyer" <amdyer@...il.com>
To:	wim@...ana.be
Cc:	linux-kernel@...r.kernel.org
Subject: watchdog behaviour on close? (watchdog-api.txt)

Hi, I am trying to implement a watchdog driver in 2.6.23 for the i.MXL
cpu (based off of drivers/char/watchdog/s3c2410_wdt.c).

I had a question about the api doc for the watchdog
(Documentation/watchdog-api.txt).  Line 37 says "When the device is
closed, the watchdog is disabled."  Later on (Line 56) it says
"Drivers will not disable the watchdog, unless a specific magic
character 'V' has been sent /dev/watchdog just before closing the
file."

I would assume that from reading L37 that the driver would
unconditionally shut down the watchdog when closing (unless
CONFIG_WATCHDOG_NOWAYOUT or the nowayout module param is specified),
but line 56 seems to contradict that.

Can you clarify the intended behaviour?

I am not subscribed to the mailing list, so please cc: replies to me.
-- 
Hardware, n.:
        The parts of a computer system that can be kicked.
--
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/