linux-kernel - Re: [PATCH] it87_wdt: Work around non-working CIR interrupts

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 PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 09 Mar 2014 19:29:16 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Marc van der Wal <x0r+kernel@....fr>,
	Wim Van Sebroeck <wim@...ana.be>
CC:	linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] it87_wdt: Work around non-working CIR interrupts

On 03/06/2014 01:36 AM, Marc van der Wal wrote:
> From: Marc van der Wal <x0r+kernel@....fr>
>
> On some hardware platforms, the it87_wdt watchdog resets the machine
> despite the watchdog daemon running and writing to /dev/watchdog.
>
> This is due to Consumer IR buffer underrun interrupts being used as
> triggers to reset the timer.  On some buggy hardware implementations
> such as the iEi AFL-12A-N270 single-board computer, this method does
> not work.
>
> However, resetting the timer by writing its original timeout value in
> its configuration register over and over again suppresses the unwanted
> reboots.
>
> Add a module option (nocir), 0 by default in order not to break existing
> setups.  Setting it to 1 enables the workaround.
>
> Fixes bug #42801 <https://bugzilla.kernel.org/show_bug.cgi?id=42801>.
> Tested primarily on Linux 3.5.7, applies cleanly on Linux 3.13.5.
>
> Signed-off-by: Marc van der Wal <x0r+kernel@....fr>

Reviewed-by: Guenter Roeck <linux@...ck-us.net>


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