This is a note to let you know that I've just added the patch titled

    Revert "percpu: free percpu allocation info for uniprocessor system"

to the 3.14-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     revert-percpu-free-percpu-allocation-info-for-uniprocessor-system.patch
and it can be found in the queue-3.14 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From bb2e226b3bef596dd56be97df655d857b4603923 Mon Sep 17 00:00:00 2001
From: Guenter Roeck <[email protected]>
Date: Sun, 21 Sep 2014 15:04:53 -0700
Subject: Revert "percpu: free percpu allocation info for uniprocessor system"

From: Guenter Roeck <[email protected]>

commit bb2e226b3bef596dd56be97df655d857b4603923 upstream.

This reverts commit 3189eddbcafc ("percpu: free percpu allocation info for
uniprocessor system").

The commit causes a hang with a crisv32 image. This may be an architecture
problem, but at least for now the revert is necessary to be able to boot a
crisv32 image.

Cc: Tejun Heo <[email protected]>
Cc: Honggang Li <[email protected]>
Signed-off-by: Guenter Roeck <[email protected]>
Signed-off-by: Tejun Heo <[email protected]>
Fixes: 3189eddbcafc ("percpu: free percpu allocation info for uniprocessor 
system")
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 mm/percpu.c |    2 --
 1 file changed, 2 deletions(-)

--- a/mm/percpu.c
+++ b/mm/percpu.c
@@ -1917,8 +1917,6 @@ void __init setup_per_cpu_areas(void)
 
        if (pcpu_setup_first_chunk(ai, fc) < 0)
                panic("Failed to initialize percpu areas.");
-
-       pcpu_free_alloc_info(ai);
 }
 
 #endif /* CONFIG_SMP */


Patches currently in stable-queue which might be from [email protected] are

queue-3.14/revert-percpu-free-percpu-allocation-info-for-uniprocessor-system.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to