linux-kernel - Re: RFC [PATCH 1/1] locking/lockdep: Fix nest lock warning on unlock

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 12 Dec 2018 10:09:01 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Derek Basehore <dbasehore@...omium.org>
Cc:     mingo@...hat.com, will.deacon@....com, linux-kernel@...r.kernel.org
Subject: Re: RFC [PATCH 1/1] locking/lockdep: Fix nest lock warning on unlock

On Tue, Dec 11, 2018 at 06:25:06PM -0800, Derek Basehore wrote:
> The function __lock_acquire checks that the nest lock is held passed
> in as an argument. The issue with this is that __lock_acquire is used
> for internal bookkeeping on lock_release. This produces a false
> positive lockdep warning on unlock. Since you explicitly don't need to
> hold the nest lock on unlock, this is an issue.

Who is triggering this?