linux-kernel - Re: [PATCH] watchdog: fix GETTIMEOUT ioctl in booke

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: <4F231877.9050504@freescale.com>
Date:	Fri, 27 Jan 2012 15:34:47 -0600
From:	Timur Tabi <timur@...escale.com>
To:	Dmitry Artamonow <mad_soft@...ox.ru>
CC:	<linux-watchdog@...r.kernel.org>,
	Kumar Gala <galak@...nel.crashing.org>,
	Wim Van Sebroeck <wim@...ana.be>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] watchdog: fix GETTIMEOUT ioctl in booke_wdt

Dmitry Artamonow wrote:
> Commit dcfb748422 ([WATCHDOG] fix book E watchdog to take
> WDIOC_SETTIMEOUT arg in seconds) fixed SETTIMEOUT ioctl
> to use seconds as a parameter instead of some hardware-specific
> "period", but missed to apply similar changes to GETTIMEOUT,
> so it still returns "period" value. Let's fix it!
> Also, while at it, make SETTIMEOUT ioctl return real timeout
> value as it should do according to the documentation.
> 
> Signed-off-by: Dmitry Artamonow <mad_soft@...ox.ru>
> ---

Acked-by: Timur Tabi <timur@...escale.com>

I don't have an easy way to test the watchdog ioctls.

-- 
Timur Tabi
Linux kernel developer at Freescale

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