On 08/01/2016 10:54 PM, Andrew Morton wrote: > On Mon, 1 Aug 2016 23:00:51 +0800 zhongjiang <zhongjiang@xxxxxxxxxx> wrote: > >> From: zhong jiang <zhongjiang@xxxxxxxxxx> >> >> At present, It is obvious that memory online and offline will fail >> when KASAN enable, > > huh, I didn't know that. Ahem... https://lkml.kernel.org/r/<20150130133552.580f73b97a9bd007979b5419@xxxxxxxxxxxxxxxxxxxx> Also commit 786a8959912eb94fc2381c2ae487a96ce55dabca kasan: disable memory hotplug Currently memory hotplug won't work with KASan. As we don't have shadow for hotplugged memory, kernel will crash on the first access to it. To make this work we will need to allocate shadow for new memory. At some future point proper memory hotplug support will be implemented. Until then, print a warning at startup and disable memory hot-add. > What's the problem and are there plans to fix it? Nobody complained, so I didn't bother to fix it. The fix for this should be simple, I'll look into this. > >> therefore, it is necessary to add the condition >> to limit the memory_hotplug when KASAN enable. >> I don't understand why we need Kconfig dependency. Why is that better than runtime warn message? >> Signed-off-by: zhong jiang <zhongjiang@xxxxxxxxxx> >> --- >> mm/Kconfig | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/mm/Kconfig b/mm/Kconfig >> index 3e2daef..f6dd77e 100644 >> --- a/mm/Kconfig >> +++ b/mm/Kconfig >> @@ -187,6 +187,7 @@ config MEMORY_HOTPLUG >> bool "Allow for memory hot-add" >> depends on SPARSEMEM || X86_64_ACPI_NUMA >> depends on ARCH_ENABLE_MEMORY_HOTPLUG >> + depends on !KASAN >> >> config MEMORY_HOTPLUG_SPARSE >> def_bool y > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>