| 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
| ||
|
Date: Thu, 24 May 2007 11:08:25 -0400 From: "Mike Frysinger" <vapier.adi@...il.com> To: "Daniel Newby" <daniel.a.newby@...il.com> Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org> Subject: Re: how to allow board writers to customize driver behavior (watchdog here) On 5/24/07, Daniel Newby <daniel.a.newby@...il.com> wrote: > On 5/24/07, Paul Mundt <lethal@...ux-sh.org> wrote: > > It sounds like your constraining your driver based on terminology. > > Watchdogs on most embedded platforms support either a 'reset' mode or > > otherwise act as periodic timers, trying to push both of these > > functionalities in to a watchdog driver is rather pointless. > > CONFIG_WATCHDOG implies 'reset' mode by definition. > > I agree for a product in the hands of a customer: let the watchdog > pull your bacon out of the fire. > > But what about debugging? Suppose your embedded computer with custom > drivers locks up solid every few hundred hours. It would be nice if > the watchdog gave a stack dump instead erasing the evidence. How about > having "action=reset" and "action=debug"? "action" corresponds one to one with the functionality of the hardware device ... what the board guy wishes to do when the interrupt expires is up to the board guy and that may include doing a debug dump somewhere ... that is most definitely not a realm i want to tread into it ;) -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/
Powered by blists - more mailing lists