| 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: <46606CBA.9020904@xes-inc.com> Date: Fri, 01 Jun 2007 14:00:10 -0500 From: Andrew Kilkenny <akilkenny@...-inc.com> To: khollis@...gate.com CC: linux-standards@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Watchdog API Update Patched from 2.6.16 Included are patches for the Watchdog API. This API is already AD HOC according to the documentation, so the update is not expected to meet much opposition. The patch/api update adds support for enabling watchdog monitoring directly via the kernel driver. It appears some drivers do this on their own, while others implement the api, dictating that userspace programs manage the watchdog. This includes adding both the ability for userspace to enable/disable the feature, and to compile in the feature to be enabled automatically at boot. The Patch file includes diffs from watchdog.h, the watchdog.txt documentation, and a KConfig file. I am unsure on the licensing information. The header file only mentions it was derived from Ken's original code. GPL information is absent, along with dates. In fact, I am unsure where the copyright belongs, if it defaults to Berkshire PC, if it must be GPL, and the like. Guidance will be greatly appreciated, especially if (absent a GPL declaration) I need permission to handle this code. - 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