linux-kernel - Re: [PATCH RFC] NMI Re-introduce un[set]_nmi

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

Message-Id: <1220535463.8609.223.camel@twins>
Date:	Thu, 04 Sep 2008 15:37:43 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Prarit Bhargava <prarit@...hat.com>
Cc:	linux-kernel@...r.kernel.org, arozansk@...hat.com,
	dzickus@...hat.com, Thomas.Mingarelli@...com, ak@...ux.intel.com,
	mingo@...e.hu
Subject: Re: [PATCH RFC] NMI Re-introduce un[set]_nmi_callback

On Thu, 2008-09-04 at 09:07 -0400, Prarit Bhargava wrote:
> Andi and Ingo,
> 
> This patch is an RFC for the following changes.  If I get a positive review,
> changes to the HP Watchdog timer (currently in the kernel) will also be
> submitted along with this patch.
> 
> Thanks,
> 
> P.
> 
> The drivers/watchdog/hpwdt.c driver requires that all NMIs are processed
> by the driver.  Currently the driver does not do this.  The first
> step is to implement code to allow the default NMI handler to be replaced
> by a custom NMI handler.

Why is the DIE_NMIWATCHDOG notifier not sufficient for this driver?

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