linux-kernel - Re: [tip:core/locking] watchdog, hpwdt: Remove priority option for NMI callback

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 26 Apr 2012 09:13:39 +0200
From:	Wim Van Sebroeck <wim@...ana.be>
To:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, peterz@...radead.org,
	thomas.mingarelli@...com, akpm@...ux-foundation.org,
	tglx@...utronix.de, dzickus@...hat.com
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:core/locking] watchdog, hpwdt: Remove priority option for NMI callback

Hi All,

> Commit-ID:  09ee10143658cd021d879ead61ead72a196302b6
> Gitweb:     http://git.kernel.org/tip/09ee10143658cd021d879ead61ead72a196302b6
> Author:     Don Zickus <dzickus@...hat.com>
> AuthorDate: Thu, 29 Mar 2012 16:11:15 -0400
> Committer:  Ingo Molnar <mingo@...nel.org>
> CommitDate: Wed, 25 Apr 2012 12:43:33 +0200
> 
> watchdog, hpwdt: Remove priority option for NMI callback
> 
> The NMI_UNKNOWN bucket only allows for one function to register
> to it. The reason for that is because only functions which can
> not determine if the NMI belongs to them or not should register
> and would like to assume/swallow any NMI they see.
> 
> As a result it doesn't make sense to let more than one function
> like this register.  In fact, letting a second function fail
> allows us to know that more than one function is going to
> swallow NMIs on the current system. This is better than silently
> being ignored.
> 
> Therefore hpwdt's priority mechanism doesn't make sense any
> more.  They will be always first on the NMI_UNKNOWN queue, if
> they register.
> 
> Removing this parameter cleans up the code and simplifies things
> for the next patch which changes how nmis are registered.
> 
> Signed-off-by: Don Zickus <dzickus@...hat.com>
> Cc: Thomas Mingarelli <thomas.mingarelli@...com>
> Cc: Wim Van Sebroeck <wim@...ana.be>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: Linus Torvalds <torvalds@...ux-foundation.org>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Link: http://lkml.kernel.org/r/1333051877-15755-2-git-send-email-dzickus@redhat.com
> Signed-off-by: Ingo Molnar <mingo@...nel.org>

This is the feedback I have from Tom which he discussed with Don:
> I don't like this patch because the Virtual NMI button doesn't come through the pretimeout routine. It is taken by the
system as an IOCK NMI error and no log messages in our IML.
> Our BIOS is not able to source the NMI.

And since then it became quiet. Imho: this needs more discussion...

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/