linux-kernel - powernow-k8: section mismatch

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <tkrat.97946ecfb316e3af@s5r6.in-berlin.de>
Date:	Tue, 25 May 2010 22:10:03 +0200 (CEST)
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	cpufreq@...r.kernel.org
cc:	Borislav Petkov <borislav.petkov@....com>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: powernow-k8: section mismatch

Hi,

I got the following with current git:

    WARNING: arch/x86/kernel/cpu/cpufreq/powernow-k8.o(.exit.text+0x1c): Section mismatch in reference from the function cleanup_module() to the variable .cpuinit.data:cpb_nb                      
    The function __exit cleanup_module() references                                                 
    a variable __cpuinitdata cpb_nb.                                                                
    This is often seen when error handling in the exit function                                     
    uses functionality in the init path.                                                            
    The fix is often to remove the __cpuinitdata annotation of                                      
    cpb_nb so it may be used outside an init section.                                               

Looks like it was introduced by
"powernow-k8: Add core performance boost support".
-- 
Stefan Richter
-=====-==-=- -=-= ==--=
http://arcgraph.de/sr/

--
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/