linux-kernel - [PATCH 0/3] watchdog: at91sam9_wdt: various fixes and improvements

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

Message-Id: <1383501164-8111-1-git-send-email-b.brezillon@overkiz.com>
Date:	Sun,  3 Nov 2013 18:52:41 +0100
From:	Boris BREZILLON <b.brezillon@...rkiz.com>
To:	Wim Van Sebroeck <wim@...ana.be>
Cc:	Fabio Porcedda <fabio.porcedda@...il.com>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	Guenter Roeck <groeck7@...il.com>,
	Yang Wenyou <wenyou.yang@...el.com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-watchdog@...r.kernel.org,
	Boris BREZILLON <b.brezillon@...rkiz.com>
Subject: [PATCH 0/3] watchdog: at91sam9_wdt: various fixes and improvements

Hello,

This patch series fix the secs_to_ticks macro in case 0 is passed as an
argument.

It also rework the heartbeat calculation to increase the security margin of the
watchdog reset timer, and use the min_heartbeat value instead of the calculated
heartbeat value for the first watchdog reset (to avoid spurious watchdog
reset).

Best Regards,

Boris

Boris BREZILLON (3):
  watchdog: at91sam9_wdt: fix secs_to_ticks
  watchdog: at91sam9_wdt: avoid spurious watchdog reset during init
  watchdog: at91sam9_wdt: increase security margin on watchdog counter
    reset

 drivers/watchdog/at91sam9_wdt.c |   38 +++++++++++++++++++++++++++-----------
 1 file changed, 27 insertions(+), 11 deletions(-)

-- 
1.7.9.5

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