linux-kernel - Re: [PATCH] lockdep: Have assert functions test for actual interrupts disabled

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: <20180906135258.GE24106@hirez.programming.kicks-ass.net>
Date:   Thu, 6 Sep 2018 15:52:58 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH] lockdep: Have assert functions test for actual
 interrupts disabled

On Wed, Sep 05, 2018 at 11:20:31AM -0400, Steven Rostedt wrote:
> 
> Peter, you OK with this patch? I'm currently triggering a bug (in rc2)
> where this patch is telling me that lockdep is getting it wrong. It
> would be good to have this upstream such that we know if it is really a
> bug in the code itself, or if lockdep didn't keep up properly.

I thought we had something for that under CONFIG_DEBUG_LOCKDEP.

/me checks and finds:

  kernel/locking/lockdep.c:check_flags()

Doesn't that work?