linux-kernel - Re: lockdep warning in check

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: <20060912202141.GA1539@slug>
Date:	Tue, 12 Sep 2006 20:21:41 +0000
From:	Frederik Deweerdt <deweerdt@...e.fr>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	arjanv@...radead.org
Subject: Re: lockdep warning in check_flags()

On Tue, Sep 12, 2006 at 06:54:48PM +0200, Ingo Molnar wrote:
> 
> * Frederik Deweerdt <deweerdt@...e.fr> wrote:
> 
> > On Mon, Sep 11, 2006 at 07:43:35AM +0200, Ingo Molnar wrote:
> > > 
> > > * Frederik Deweerdt <deweerdt@...e.fr> wrote:
> > > 
> > > > Lockdep issues the following warning:
> > > > 
> > > > [   16.835268] Freeing unused kernel memory: 260k freed
> > > > [   16.842715] Write protecting the kernel read-only data: 432k
> > > > [   17.796518] BUG: warning at kernel/lockdep.c:2359/check_flags()
> > > 
> > > this warning means that the "soft" and "hard" hardirqs-disabled state 
> > > got out of sync: the irqtrace tracking code thinks that hardirqs are 
> > > disabled, while in reality they are enabled. The thing to watch for are 
> > > new "stii" instructions in entry.S (and other assembly code), without a 
> > > matching TRACE_HARDIRQS_ON call. [Another, rarer possiblity is NMI code 
> > > saving/restoring interrupts - do you have NMIs enabled? (are there any 
> > > NMI counts in /proc/interrupts?)]
> > NMIs were disabled. But I've just booted -mm2 and the warning went away.
> > Could this be related to the recent pda changes?
> 
> yeah, it could be related to the fix below. Can you confirm that by 
> applying this to your -mm1 tree the message goes away?
> 
It does, thanks Ingo.
Frederik
-
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/