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
>
