Re: Linux 2.6.28-rc1

[Rufus & Azrael <rufus-azrael@numericable.fr>]

[-- Attachment #1: Type: text/plain, Size: 94 bytes --]

Hi all,


Here are my compilation warnings and section mismatches for 2.6.28-rc1.

Regards.



[-- Attachment #2: section_mismatch_2_6_28-rc1 --]
[-- Type: text/plain, Size: 4842 bytes --]

arch/x86/kernel/cpu/mtrr/main.c: In function ‘mtrr_cleanup’:
arch/x86/kernel/cpu/mtrr/main.c:1363: attention : ‘gran_factor’ may be used uninitialized in this function
arch/x86/kernel/cpu/mtrr/main.c:1364: attention : ‘gran_base’ may be used uninitialized in this function

fixed by patch in http://marc.info/?l=linux-kernel&m=122394648405506&w=2 but not yet in mainline
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WARNING: kernel/built-in.o(.text+0x14d39): Section mismatch in reference from the function reserve_region_with_split() to the function .init.text:__reserve_region_with_split()
The function reserve_region_with_split() references
the function __init __reserve_region_with_split().
This is often because reserve_region_with_split lacks a __init 
annotation or the annotation of __reserve_region_with_split is wrong.

WARNING: vmlinux.o(.text+0x38469): Section mismatch in reference from the function reserve_region_with_split() to the function .init.text:__reserve_region_with_split()
The function reserve_region_with_split() references
the function __init __reserve_region_with_split().
This is often because reserve_region_with_split lacks a __init 
annotation or the annotation of __reserve_region_with_split is wrong.

fixed by patch in http://lkml.org/lkml/2008/10/12/38 but not yet in mainline 
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WARNING: drivers/built-in.o(.init.text+0xaf2f): Section mismatch in reference from the function hid_init() to the function .exit.text:hidraw_exit()
The function __init hid_init() references
a function __exit hidraw_exit().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
hidraw_exit() so it may be used outside an exit section.

WARNING: drivers/hid/hid.o(.init.text+0x5e): Section mismatch in reference from the function hid_init() to the function .exit.text:hidraw_exit()
The function __init hid_init() references
a function __exit hidraw_exit().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
hidraw_exit() so it may be used outside an exit section.

WARNING: vmlinux.o(.init.text+0x2598a): Section mismatch in reference from the function hid_init() to the function .exit.text:hidraw_exit()
The function __init hid_init() references
a function __exit hidraw_exit().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
hidraw_exit() so it may be used outside an exit section.

fixed by patch in http://marc.info/?l=linux-kernel&m=122425994132500&w=2 but not yet in mainline
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WARNING: arch/x86/kernel/built-in.o(.cpuinit.text+0x347): Section mismatch in reference from the function fpu_init() to the function .init.text:init_thread_xstate()
The function __cpuinit fpu_init() references
a function __init init_thread_xstate().
If init_thread_xstate is only used by fpu_init then
annotate init_thread_xstate with a matching annotation.

WARNING: vmlinux.o(.cpuinit.text+0x605): Section mismatch in reference from the function fpu_init() to the function .init.text:init_thread_xstate()
The function __cpuinit fpu_init() references
a function __init init_thread_xstate().
If init_thread_xstate is only used by fpu_init then
annotate init_thread_xstate with a matching annotation.

WARNING: kernel/built-in.o(.text+0x10838): Section mismatch in reference from the function notify_cpu_starting() to the variable .cpuinit.data:cpu_chain
The function notify_cpu_starting() references
the variable __cpuinitdata cpu_chain.
This is often because notify_cpu_starting lacks a __cpuinitdata 
annotation or the annotation of cpu_chain is wrong.

WARNING: vmlinux.o(.text+0x33f68): Section mismatch in reference from the function notify_cpu_starting() to the variable .cpuinit.data:cpu_chain
The function notify_cpu_starting() references
the variable __cpuinitdata cpu_chain.
This is often because notify_cpu_starting lacks a __cpuinitdata 
annotation or the annotation of cpu_chain is wrong.

fixed by patch in http://lkml.org/lkml/2008/10/22/654 but not yet in mainline
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------