linux-kernel - Re: [PATCH 2/2] tracing: Use proper do_arch_spin

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20220922084019.4e2f2afc@gandalf.local.home>
Date:   Thu, 22 Sep 2022 08:40:19 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Waiman Long <longman@...hat.com>, Ingo Molnar <mingo@...hat.com>,
        Will Deacon <will@...nel.org>,
        Boqun Feng <boqun.feng@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] tracing: Use proper do_arch_spin_lock() API

On Thu, 22 Sep 2022 09:55:29 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> > Nothing here is needed, as interrupts had better be disabled when this
> > function is called. And there's already a:
> > 
> > 	WARN_ON_ONCE(!irqs_disabled());  
> 
> You can write that as lockdep_assert_irqs_disabled();

Of course we can ;-)  But this was written before that existed.

-- Steve