linux-kernel - Re: lockdep warning: threadirqs and preemptoff tracer

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:	Tue, 26 May 2015 09:04:08 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Daniel Wagner <daniel.wagner@...-carit.de>
Cc:	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: lockdep warning: threadirqs and preemptoff tracer

On Tue, 26 May 2015 14:51:28 +0200
Daniel Wagner <daniel.wagner@...-carit.de> wrote:


> > Don't you want to modify __local_bh_enable_ip()?
> 
> __do_softirq() calls __local_bh_disable_ip() and __local_bh_enable() and
> not __local_bh_enable_ip(). I have no clue why this is done this way.
> Need to look into the history.

Yeah, that probably needs to be fixed. Find out why we call *_ip() and
it would make more sense to make that symmetric, as it may break
something else otherwise.

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