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
| ||
|
Date: Wed, 19 Apr 2017 19:20:19 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Byungchul Park <byungchul.park@....com> Cc: mingo@...nel.org, tglx@...utronix.de, walken@...gle.com, boqun.feng@...il.com, kirill@...temov.name, linux-kernel@...r.kernel.org, linux-mm@...ck.org, iamjoonsoo.kim@....com, akpm@...ux-foundation.org, willy@...radead.org, npiggin@...il.com, kernel-team@....com Subject: Re: [PATCH v6 05/15] lockdep: Implement crossrelease feature On Tue, Mar 14, 2017 at 05:18:52PM +0900, Byungchul Park wrote: > +config LOCKDEP_CROSSRELEASE > + bool "Lock debugging: make lockdep work for crosslocks" > + select PROVE_LOCKING depends PROVE_LOCKING instead ? > + default n > + help > + This makes lockdep work for crosslock which is a lock allowed to > + be released in a different context from the acquisition context. > + Normally a lock must be released in the context acquiring the lock. > + However, relexing this constraint helps synchronization primitives > + such as page locks or completions can use the lock correctness > + detector, lockdep. > + > config PROVE_LOCKING > bool "Lock debugging: prove locking correctness" > depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT > -- > 1.9.1 >
Powered by blists - more mailing lists