linux-kernel - Re: [PATCH -tip 2/2 resend] x86, traps: Drop nmi_reason

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: <20110302194611.GZ11359@redhat.com>
Date:	Wed, 2 Mar 2011 14:46:11 -0500
From:	Don Zickus <dzickus@...hat.com>
To:	Cyrill Gorcunov <gorcunov@...nvz.org>
Cc:	Ingo Molnar <mingo@...e.hu>, "Huang, Ying" <ying.huang@...el.com>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip 2/2 resend] x86, traps: Drop nmi_reason_lock until
 it is really needed

On Wed, Mar 02, 2011 at 10:14:08PM +0300, Cyrill Gorcunov wrote:
> > 
> > Now this spinlock doesn't affect them, because they registered an nmi
> > handler to catch it and dump their stack (I modified the code to use
> > DIE_NMIUNKNOWN instead of DIE_NMI to avoid conflict with the
> > nmi_watchdog).  But I don't know what the affect is, if that spinlock is
> > not there (I sent a private email to SGI inquiring, their guy wasn't
> > around this week).
> 
>   Don, do you know -- was new nmi-watchdog system tested with UV machine
> somewhere?

They are testing it now, I am working through the issues with them.

Cheers,
Don
--
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/