diff options
Diffstat (limited to 'include/linux/init.h')
| -rw-r--r-- | include/linux/init.h | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/include/linux/init.h b/include/linux/init.h index de994304e0bb..577671c55153 100644 --- a/include/linux/init.h +++ b/include/linux/init.h | |||
| @@ -46,16 +46,23 @@ | |||
| 46 | #define __exitdata __section(.exit.data) | 46 | #define __exitdata __section(.exit.data) |
| 47 | #define __exit_call __used __section(.exitcall.exit) | 47 | #define __exit_call __used __section(.exitcall.exit) |
| 48 | 48 | ||
| 49 | /* modpost check for section mismatches during the kernel build. | 49 | /* |
| 50 | * modpost check for section mismatches during the kernel build. | ||
| 50 | * A section mismatch happens when there are references from a | 51 | * A section mismatch happens when there are references from a |
| 51 | * code or data section to an init section (both code or data). | 52 | * code or data section to an init section (both code or data). |
| 52 | * The init sections are (for most archs) discarded by the kernel | 53 | * The init sections are (for most archs) discarded by the kernel |
| 53 | * when early init has completed so all such references are potential bugs. | 54 | * when early init has completed so all such references are potential bugs. |
| 54 | * For exit sections the same issue exists. | 55 | * For exit sections the same issue exists. |
| 56 | * | ||
| 55 | * The following markers are used for the cases where the reference to | 57 | * The following markers are used for the cases where the reference to |
| 56 | * the *init / *exit section (code or data) is valid and will teach | 58 | * the *init / *exit section (code or data) is valid and will teach |
| 57 | * modpost not to issue a warning. | 59 | * modpost not to issue a warning. Intended semantics is that a code or |
| 58 | * The markers follow same syntax rules as __init / __initdata. */ | 60 | * data tagged __ref* can reference code or data from init section without |
| 61 | * producing a warning (of course, no warning does not mean code is | ||
| 62 | * correct, so optimally document why the __ref is needed and why it's OK). | ||
| 63 | * | ||
| 64 | * The markers follow same syntax rules as __init / __initdata. | ||
| 65 | */ | ||
| 59 | #define __ref __section(.ref.text) noinline | 66 | #define __ref __section(.ref.text) noinline |
| 60 | #define __refdata __section(.ref.data) | 67 | #define __refdata __section(.ref.data) |
| 61 | #define __refconst __section(.ref.rodata) | 68 | #define __refconst __section(.ref.rodata) |
