The patch titled
cpuset: mempolicy migration typo fix
has been added to the -mm tree. Its filename is
cpuset-mempolicy-migration-typo-fix.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: cpuset: mempolicy migration typo fix
From: Paul Jackson <pj@xxxxxxx>
Mistyped an ifdef CONFIG_CPUSETS - fixed.
I doubt that anyone ever noticed. The impact of this typo was
that if someone:
1) was using MPOL_BIND to force off node allocations
2) while using cpusets to constrain memory placement
3) when that cpuset was migrating that jobs memory
4) while the tasks in that job were actively forking
then there was a rare chance that future allocations using
that MPOL_BIND policy would be node local, not off node.
Signed-off-by: Paul Jackson <pj@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
include/linux/mempolicy.h | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN include/linux/mempolicy.h~cpuset-mempolicy-migration-typo-fix include/linux/mempolicy.h
--- a/include/linux/mempolicy.h~cpuset-mempolicy-migration-typo-fix
+++ a/include/linux/mempolicy.h
@@ -150,7 +150,7 @@ extern void mpol_rebind_mm(struct mm_str
extern void mpol_fix_fork_child_flag(struct task_struct *p);
#define set_cpuset_being_rebound(x) (cpuset_being_rebound = (x))
-#ifdef CONFIG_CPUSET
+#ifdef CONFIG_CPUSETS
#define current_cpuset_is_being_rebound() \
(cpuset_being_rebound == current->cpuset)
#else
_
Patches currently in -mm which might be from pj@xxxxxxx are
highest_possible_node_id-linkage-fix.patch
cpuset-mempolicy-migration-typo-fix.patch
memory-page-alloc-minor-cleanups.patch
memory-page-alloc-minor-cleanups-fix.patch
memory-page_alloc-zonelist-caching-speedup.patch
memory-page_alloc-zonelist-caching-reorder-structure.patch
cpuset-minor-code-refinements.patch
cpuset-remove-sched-domain-hooks-from-cpusets.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
