We found 2 bugs while we test and develop memory hotplug. The hotplug code does not handle node_states[N_NORMAL_MEMORY] correctly, it may corrupt the memory.
And we ensure the SLUB do NOT respond when node_states[N_NORMAL_MEMORY] is not changed. The patchset is based on mainline(3d0ceac129f3ea0b125289055a3aa7519d38df77) CC: David Rientjes <rient...@google.com> Cc: Minchan Kim <minchan....@gmail.com> CC: KOSAKI Motohiro <kosaki.motoh...@jp.fujitsu.com> CC: Yasuaki Ishimatsu <isimatu.yasu...@jp.fujitsu.com> CC: Rob Landley <r...@landley.net> CC: Andrew Morton <a...@linux-foundation.org> CC: Jiang Liu <jiang....@huawei.com> CC: Kay Sievers <kay.siev...@vrfy.org> CC: Greg Kroah-Hartman <gre...@suse.de> CC: Mel Gorman <mgor...@suse.de> CC: 'FNST-Wen Congyang' <we...@cn.fujitsu.com> CC: linux-...@vger.kernel.org CC: linux-kernel@vger.kernel.org CC: linux...@kvack.org Lai Jiangshan (2): memory_hotplug: fix possible incorrect node_states[N_NORMAL_MEMORY] slub, hotplug: ignore unrelated node's hot-adding and hot-removing Documentation/memory-hotplug.txt | 5 +- include/linux/memory.h | 1 + mm/memory_hotplug.c | 136 +++++++++++++++++++++++++++++++++----- mm/slub.c | 4 +- 4 files changed, 127 insertions(+), 19 deletions(-) -- 1.7.4.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
