linux-kernel - config RCU_EQS

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

Date:	Fri, 3 Jul 2015 10:07:45 +0200
From:	Jean Delvare <jdelvare@...e.de>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: config RCU_EQS_DEBUG

Hi Paul,

You just introduced a Linux kernel configuration option named
RCU_EQS_DEBUG. Its short description is "Use this when adding any sort
of NO_HZ support to your arch".

I'm afraid this is a bad way to briefly explain what the option
actually does (which is what the short description is for.) A sentence
like "use this when adding any sort of NO_HZ support to your arch"
should go in the help text, not the short description. The short
description should be something like along the lines of "Enable
consistency checks for RCU", for example.

Additionally I see some inconsistency in the fact that this option
defaults to n but the help text says "Say Y if you are unsure". BTW,
option RCU_CPU_STALL_INFO is equally inconsistent with a default y and
"say N if you are unsure" in the help text.

-- 
Jean Delvare
SUSE L3 Support
--
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/