path: root/arch
diff options
authorPaul Mackerras <paulus@samba.org>2005-05-20 16:57:22 +1000
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-05-20 07:54:10 -0700
commit6c37a88c5b1195d4ac74d44a6413839b93df5af4 (patch)
tree3b829314447f53686bc028dd32f614bb4a8a1cbc /arch
parentFix get_unmapped_area sanity tests (diff)
[PATCH] ppc32: don't call progress functions after boot
On ppc32, the platform code can supply a "progress" function that is used to show progress through the boot. These functions are usually in an init section and so can't be called after the init pages are freed. Now that the cpu bringup code can be called after the system is booted (for hotplug cpu) we can get the situation where the progress function can be called after boot. The simple fix is to set the progress function pointer to NULL when the init pages are freed, and that is what this patch does (note that all callers already check whether the function pointer is NULL before trying to call it). Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to '')
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/ppc/mm/init.c b/arch/ppc/mm/init.c
index be02a7fec2b7..363c157e3617 100644
--- a/arch/ppc/mm/init.c
+++ b/arch/ppc/mm/init.c
@@ -179,6 +179,7 @@ void free_initmem(void)
if (!have_of)
+ ppc_md.progress = NULL;
#undef FREESEC