linux-kernel - Re: [PATCH 22/24] i386: add TRACE_IRQS

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: <1231785815.4371.205.camel@laptop>
Date:	Mon, 12 Jan 2009 19:43:35 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	heukelum@...tmail.fm, linux-kernel@...r.kernel.org, ak@...e.de,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Subject: Re: [PATCH 22/24] i386: add TRACE_IRQS_OFF for the nmi

On Mon, 2009-01-12 at 19:39 +0100, Ingo Molnar wrote:
> * Peter Zijlstra <peterz@...radead.org> wrote:
> 
> > On Tue, 2008-09-09 at 21:56 +0200, heukelum@...tmail.fm wrote:
> > > From: Alexander van Heukelum <heukelum@...tmail.fm>
> > > 
> > > At this point interrupts are off, so let's inform the tracing
> > > code of that fact before calling into C.
> > 
> > Sorry but this is an obvious dud, lockdep (and thus the irq state
> > tracer) aren't nmi safe.
> > 
> > Ingo, please revert, as people are already seeing lockdep warnings due
> > to this.
> 
> done - reverted it in tip/x86/urgent, see the commit below. Is that all 
> that we need, wasnt there a 64-bit side done too?

I had a _very_ quick peek but couldn't fine one, Alexander, does your
memory go back that far? :-)


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