linux-kernel - Re: [RFC] [PATCH 0/10] Generic Watchdog Timer Driver

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

Message-ID: <20110617071118.GJ23305@infomag.iguana.be>
Date:	Fri, 17 Jun 2011 09:11:18 +0200
From:	Wim Van Sebroeck <wim@...ana.be>
To:	Andrea Galbusera <gizero@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux Watchdog Mailing List <linux-watchdog@...r.kernel.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [RFC] [PATCH 0/10] Generic Watchdog Timer Driver

Hi Andrea,

> On Wed, Feb 23, 2011 at 9:41 PM, Wim Van Sebroeck <wim@...ana.be> wrote:
> > To reduce copying the same code over and over in each watchdog device driver, Alan Cox and myself constructed a new framework/API that consolidates the common watchdog timer driver functions.
> >
> > This framework/API consists of the following patches:
> > part  1: Introduction of the WatchDog Timer Driver Core
> > part  2: Add the basic ioctl functionality
> > part  3: Add the WDIOC_KEEPALIVE ioctl
> > part  4: Add the WDIOC_SETOPTIONS ioctl
> > part  5: Add the WDIOC_SETTIMEOUT and WDIOC_GETTIMEOUT ioctl
> > part  6: Add orphan control
> > part  7: Add the Magic Close feature
> > part  8: Add the nowayout feature
> > part  9: Add support for a miscdev parent device
> > part 10: Add support for extra ioctl calls
> 
> While looking for efforts to provide a generic driver for gpio driven
> watchdog devices, like some simple hardware supervisors, I came into
> this patchset RFC, which turned out to be very interesting to me.
> Maybe I'm looking into the wrong places, but I could not find any
> upstream commit after this RFC.
> Since I don't see any real critic from commenters to the approach you
> are suggesting, I'd like to know if there still is some
> work-in-progress on this.

I was working on it yesterday and will finish testing today.
So expect a new post this afternoon.

I incorporated the comments I received. Orphan control will not be in (as
long as the watchdog device is registered you can reopen it). And we will
add the minimum and maximum timeout in an extra part.

Kind regards,
Wim.

--
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/