linux-kernel - Re: [PATCH] ww-mutex: clarify help text for DEBUG_WW_MUTEX

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

Message-ID: <53FDF8DB.6050703@canonical.com>
Date:	Wed, 27 Aug 2014 17:27:23 +0200
From:	Maarten Lankhorst <maarten.lankhorst@...onical.com>
To:	Rob Clark <robdclark@...il.com>, linux-kernel@...r.kernel.org
CC:	Daniel Vetter <daniel@...ll.ch>, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH] ww-mutex: clarify help text for DEBUG_WW_MUTEX_SLOWPATH

Acked-by: Maarten Lankhorst <maarten.lankhorst@...onical.com>

On 27-08-14 17:19, Rob Clark wrote:
> We really don't want distro's enabling this in their kernels.  Try and
> make that more clear.
> 
> Signed-off-by: Rob Clark <robdclark@...il.com>
> ---
>  lib/Kconfig.debug | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 07c2832..1b233fc 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -892,6 +892,10 @@ config DEBUG_WW_MUTEX_SLOWPATH
>  	 the full mutex checks enabled with (CONFIG_PROVE_LOCKING) this
>  	 will test all possible w/w mutex interface abuse with the
>  	 exception of simply not acquiring all the required locks.
> +	 Note that this feature can introduce significant overhead, so
> +	 it really should not be enabled in a production or distro kernel,
> +	 even a debug kernel.  If you are a driver writer, enable it.  If
> +	 you are a distro, do not.
>  
>  config DEBUG_LOCK_ALLOC
>  	bool "Lock debugging: detect incorrect freeing of live locks"
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/