| 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: Tue, 30 Sep 2008 11:28:40 +0800 From: Lai Jiangshan <laijs@...fujitsu.com> To: Ingo Molnar <mingo@...e.hu> CC: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: [PATCH] markers: let marker_debug as module parameter if we want to enable marker debug output, we have to modify the code and remake/reinstall the kernel in current code. this patch enable marker_debug to be set when kernel start. Signed-off-by: Lai Jiangshan <laijs@...fujitsu.com> --- diff --git a/kernel/marker.c b/kernel/marker.c index 9f76c4a..5d8404f 100644 --- a/kernel/marker.c +++ b/kernel/marker.c @@ -28,8 +28,9 @@ extern struct marker __start___markers[]; extern struct marker __stop___markers[]; -/* Set to 1 to enable marker debug output */ -static const int marker_debug; +static int marker_debug; +module_param(marker_debug, bool, 0); +MODULE_PARM_DESC(marker_debug, "Set to 1 to enable marker debug output"); /* * markers_mutex nests inside module_mutex. Markers mutex protects the builtin -- 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/
Powered by blists - more mailing lists