linux-kernel - Re: [PATCH] x86: fix duplicate calls of the nmi handler

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]

Date:	Fri, 10 Sep 2010 18:15:16 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Robert Richter <robert.richter@....com>
Cc:	Ingo Molnar <mingo@...e.hu>, Don Zickus <dzickus@...hat.com>,
	"gorcunov@...il.com" <gorcunov@...il.com>,
	"fweisbec@...il.com" <fweisbec@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ying.huang@...el.com" <ying.huang@...el.com>,
	"ming.m.lin@...el.com" <ming.m.lin@...el.com>,
	"yinghai@...nel.org" <yinghai@...nel.org>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	"eranian@...gle.com" <eranian@...gle.com>
Subject: Re: [PATCH] x86: fix duplicate calls of the nmi handler

On Fri, 2010-09-10 at 17:56 +0200, Robert Richter wrote:
> On 10.09.10 10:46:34, Ingo Molnar wrote:
> > > > I'll look at getting a trace of the thing, but if any of you has
> a
> > > > bright idea...
> 
> I found another patch in my queue, which fixes a duplicate call of the
> nmi handler. Since I could not yet reproduce the bug, I am not sure if
> this fixes the problem, but it is worth a try.
> 
> 

           <...>-6114  [001]   340.053060: perf_event_nmi_handler: NMI-handled(1): 34833 27411 1
           <...>-6114  [001]   340.053061: perf_event_nmi_handler: NMI-stop: 34833 27411 1
           <...>-6114  [001]   340.053062: perf_event_nmi_handler: NMI: 34834 27411 1
           <...>-6114  [001]   340.053063: x86_pmu_handle_irq: OVERFLOW: 1
           <...>-6114  [001]   340.053064: x86_pmu_handle_irq: HANDLED: 1
           <...>-6114  [001]   340.053067: perf_event_nmi_handler: NMI-handled(1): 34834 27411 1
           <...>-6114  [001]   340.053068: perf_event_nmi_handler: NMI-stop: 34834 27411 1
           <...>-6114  [001]   340.053069: perf_event_nmi_handler: NMI: 34835 27411 1
           <...>-6114  [001]   340.053070: perf_event_nmi_handler: NMI-handled(0): 34835 27411 1
           <...>-6114  [001]   340.053071: perf_event_nmi_handler: NMI: 34835 27411 1
           <...>-6114  [001]   340.053072: perf_event_nmi_handler: NMI: 34835 27411 1
           <...>-6114  [001]   340.053073: perf_event_nmi_handler: NMI-fail


Nope.. it doesn't get tagged because handled == 1, not > 1.
--
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/