linux-kernel - [PATCH] Fix section mismatch cpu_notify_nofail() -> cpu

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>] [day] [month] [year] [list]

Message-Id: <4c000142282429edd0@agluck-desktop.sc.intel.com>
Date:	Fri, 28 May 2010 10:45:38 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH] Fix section mismatch cpu_notify_nofail() -> cpu_chain

WARNING: Section mismatch in reference from the function cpu_notify_nofail()
         to the variable .cpuinit.data:cpu_chain
    
It appears that "cpu_chain" should not be marked as __cpuinitdata.
    
Signed-off-by: Tony Luck <tony.luck@...el.com>

---

diff --git a/kernel/cpu.c b/kernel/cpu.c
index 3097382..84d66a0 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -34,7 +34,7 @@ void cpu_maps_update_done(void)
 	mutex_unlock(&cpu_add_remove_lock);
 }
 
-static __cpuinitdata RAW_NOTIFIER_HEAD(cpu_chain);
+static RAW_NOTIFIER_HEAD(cpu_chain);
 
 /* If set, cpu_up and cpu_down will return -EBUSY and do nothing.
  * Should always be manipulated under cpu_add_remove_lock
--
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/