[PATCH v3] memory hotplug: update the variables after memory removed

Commit ea0854170c95 ("memory hotplug: fix a bug on /dev/mem for 64-bit kernels") added a fuction update_end_of_memory_vars() to update high_memory, max_pfn and max_low_pfn. Here we may access wrong memory via /dev/mem after memory remove without this patch. I modified the function and call it in

[PATCH v3] memory hotplug: update the variables after memory removed

Commit ea0854170c95 ("memory hotplug: fix a bug on /dev/mem for 64-bit kernels") added a fuction update_end_of_memory_vars() to update high_memory, max_pfn and max_low_pfn. Here we may access wrong memory via /dev/mem after memory remove without this patch. I modified the function and call it in

[PATCH v3] memory hotplug: update the variables after memory removed

Commit ea0854170c95 (memory hotplug: fix a bug on /dev/mem for 64-bit kernels) added a fuction update_end_of_memory_vars() to update high_memory, max_pfn and max_low_pfn. Here we may access wrong memory via /dev/mem after memory remove without this patch. I modified the function and call it in

[PATCH v3] memory hotplug: update the variables after memory removed

Commit ea0854170c95 (memory hotplug: fix a bug on /dev/mem for 64-bit kernels) added a fuction update_end_of_memory_vars() to update high_memory, max_pfn and max_low_pfn. Here we may access wrong memory via /dev/mem after memory remove without this patch. I modified the function and call it in