diff options
author | Sam Ravnborg <sam@ravnborg.org> | 2007-05-17 20:14:48 +0200 |
---|---|---|
committer | Sam Ravnborg <sam@ravnborg.org> | 2007-05-19 09:11:58 +0200 |
commit | 0e0d314e6a01bb14d303e35e6f7ba24b17020044 (patch) | |
tree | 596929a373bbbba7c2d7af4ae6e485a4c584b76f /include/linux/init.h | |
parent | ca967258b69eb65dcb07bbab90fdf964c6d2ec45 (diff) | |
download | linux-stable-0e0d314e6a01bb14d303e35e6f7ba24b17020044.tar.gz linux-stable-0e0d314e6a01bb14d303e35e6f7ba24b17020044.tar.bz2 linux-stable-0e0d314e6a01bb14d303e35e6f7ba24b17020044.zip |
kbuild: introduce __init_refok/__initdata_refok to supress section mismatch warnings
Throughout the kernel there are a few legitimite references
to init or exit sections. Most of these are covered by the
patterns included in modpost but a few nees special attention.
To avoid hardcoding a lot of function names in modpost introduce
a marker so relevant function/data can be marked.
When modpost see a reference to a init/exit function from
a function/data marked no warning will be issued.
Idea from: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'include/linux/init.h')
-rw-r--r-- | include/linux/init.h | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/include/linux/init.h b/include/linux/init.h index e007ae4dc41e..56ec4c62eee0 100644 --- a/include/linux/init.h +++ b/include/linux/init.h @@ -45,6 +45,19 @@ #define __exitdata __attribute__ ((__section__(".exit.data"))) #define __exit_call __attribute_used__ __attribute__ ((__section__ (".exitcall.exit"))) +/* modpost check for section mismatches during the kernel build. + * A section mismatch happens when there are references from a + * code or data section to an init section (both code or data). + * The init sections are (for most archs) discarded by the kernel + * when early init has completed so all such references are potential bugs. + * For exit sections the same issue exists. + * The following markers are used for the cases where the reference to + * the init/exit section (code or data) is valid and will teach modpost + * not to issue a warning. + * The markers follow same syntax rules as __init / __initdata. */ +#define __init_refok noinline __attribute__ ((__section__ (".text.init.refok"))) +#define __initdata_refok __attribute__ ((__section__ (".data.init.refok"))) + #ifdef MODULE #define __exit __attribute__ ((__section__(".exit.text"))) #else |