linux-kernel - Re: adding lockdep support to the Blackfin arch

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: <20090609063208.GA3983@elte.hu>
Date:	Tue, 9 Jun 2009 08:32:08 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mike Frysinger <vapier.adi@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Ingo Molnar <mingo@...hat.com>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: adding lockdep support to the Blackfin arch


* Mike Frysinger <vapier.adi@...il.com> wrote:

> ive been extending the Blackfin arch recently to support lockdep.
> since i also had to implement irqflags/stacktrace as well, i wouldnt
> be surprised if this issue is nested in there, plus this is a no-mmu
> system.
> 
> at any rate, when i boot up a Blackfin system with PROVE_LOCKING
> enabled, i end up with this warning:
> Badness at kernel/fork.c:988
> 
> which correlates to this in copy_process():
>     DEBUG_LOCKS_WARN_ON(!p->hardirqs_enabled);

This suggests that the irqflags tracking might be wrong: the fork 
code expects it at this point that hardirqs are enabled.

> btw, in order to get this to work in the first place, i had to 
> extend

[incomplete mail?]

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