lkml.org 
[lkml]   [2014]   [Jul]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH v2 1/8] init.h: Add __init_str / __exit_str macros
Date
Add macros to be able to mark string literals used in __init / __exit
functions.

Signed-off-by: Mathias Krause <minipli@googlemail.com>

---
v2: - use a better code example
---
include/linux/init.h | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)

diff --git a/include/linux/init.h b/include/linux/init.h
index 2df8e8dd10..2c1cf10bb7 100644
--- a/include/linux/init.h
+++ b/include/linux/init.h
@@ -35,6 +35,20 @@
* Don't forget to initialize data not at file scope, i.e. within a function,
* as gcc otherwise puts the data into the bss section and not into the init
* section.
+ *
+ * For strings used in __init / __exit functions the __init_str() /
+ * __exit_str() macros will take care of marking the strings accordingly so
+ * they can be freed, too. Otherwise the strings would resist in memory, even
+ * though they are no longer referenced.
+ *
+ * Use them like this:
+ *
+ * static int __init my_setup(char *arg)
+ * {
+ * if (!strcmp(arg, __init_str("disable")))
+ * enabled = false;
+ * }
+ * __setup("mydev=", my_setup);
*/

/* These are for everybody (although not all archs will actually
@@ -45,6 +59,12 @@
#define __exitdata __section(.exit.data)
#define __exit_call __used __section(.exitcall.exit)

+/* Those can be used to mark strings used in __init / __exit functions. */
+#define __init_str(str) __mark_str(str, __UNIQUE_ID(_init_str_), __initconst)
+#define __exit_str(str) __mark_str(str, __UNIQUE_ID(_exit_str_), __exitdata)
+#define __mark_str(str, var, __section) \
+ ({ static const char var[] __section __aligned(1) = str; var; })
+
/*
* Some architecture have tool chains which do not handle rodata attributes
* correctly. For those disable special sections for const, so that other
--
1.7.10.4


\
 
 \ /
  Last update: 2014-07-12 17:21    [W:0.075 / U:0.592 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site