linux-kernel - Re: [PATCH 1/2] security/apparmor: Replace homebrew use of write_can

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, 3 Oct 2017 17:07:09 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Will Deacon <will.deacon@....com>
Cc:     linux-kernel@...r.kernel.org, john.johansen@...onical.com,
        paulmck@...ux.vnet.ibm.com
Subject: Re: [PATCH 1/2] security/apparmor: Replace homebrew use of
 write_can_lock with lockdep

On Tue, Oct 03, 2017 at 03:32:45PM +0100, Will Deacon wrote:
> The lockdep subsystem provides a robust way to assert that a lock is
> held, so use that instead of write_can_lock, which can give incorrect
> results for qrwlocks.
> 
> Cc: John Johansen <john.johansen@...onical.com>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Signed-off-by: Will Deacon <will.deacon@....com>

Thanks Will, good to be able to finally remove that API.