memory hotplug: Refuse to add unaligned memory regions
Subsystems (2)
PATCH 1/1 memory hotplug: Refuse to add unaligned memory regions
The sysfs memory probe interface allows unaligned regions to be added:
# echo 0xffffff > /sys/devices/system/memory/probe
# cat /proc/iomem 00ffffff-01fffffe : System RAM 01ffffff-02fffffe : System RAM 02ffffff-03fffffe : System RAM 03ffffff-04fffffe : System RAM 04ffffff-05fffffe : System RAM
Return -EINVAL instead of creating these bad regions.
---
drivers/base/memory.c +4 -0
@@ -380,9 +380,13 @@ memory_probe_store(struct class *class,u64 phys_addr;int nid;int i, ret; +unsigned long pages_per_block =PAGES_PER_SECTION * sections_per_block; phys_addr =simple_strtoull (buf,NULL ,0 ); +if (phys_addr & ((pages_per_block <<PAGE_SHIFT ) -1 )) +return -EINVAL ; +for (i =0 ; i < sections_per_block; i++) { nid =memory_add_physaddr_to_nid (phys_addr); ret = add_memory(nid, phys_addr,
Quoted 13 lines · Anton Blanchard
The sysfs memory probe interface allows unaligned regions to be added:
# echo 0xffffff > /sys/devices/system/memory/probe# cat /proc/iomem 00ffffff-01fffffe : System RAM 01ffffff-02fffffe : System RAM 02ffffff-03fffffe : System RAM 03ffffff-04fffffe : System RAM 04ffffff-05fffffe : System RAM
Quoted 4 lines
Return
-EINVALinstead of creating these bad regions.Signed-off-by Anton Blanchard <[email protected]>---
Is this something that should go into 3.1 and older kernels to properly handle this type of error?
greg k-h
Quoted 4 lines · On Thu, 15 Sep 2011 06:26:15 +1000 Anton Blanchard <[email protected]> wrote:
The sysfs memory probe interface allows unaligned regions to be added:
Quoted 8 lines
# echo 0xffffff > /sys/devices/system/memory/probe# cat /proc/iomem 00ffffff-01fffffe : System RAM 01ffffff-02fffffe : System RAM 02ffffff-03fffffe : System RAM 03ffffff-04fffffe : System RAM 04ffffff-05fffffe : System RAM
Then don't do that?
Quoted 27 lines · Anton Blanchard
The sysfs memory probe interface allows unaligned regions to be added:
# echo 0xffffff> /sys/devices/system/memory/probe# cat /proc/iomem 00ffffff-01fffffe : System RAM 01ffffff-02fffffe : System RAM 02ffffff-03fffffe : System RAM 03ffffff-04fffffe : System RAM 04ffffff-05fffffe : System RAMReturn
-EINVALinstead of creating these bad regions.Signed-off-by Anton Blanchard<[email protected]>---
Index:
linux-build/drivers/base/memory.c
===================================================================drivers/base/memory.c +1
-0@@ -380,9 +380,13 @@ memory_probe_store(struct class *class,u64 phys_addr;int nid;int i, ret; +unsigned long pages_per_block =PAGES_PER_SECTION * sections_per_block;
drivers/base/memory.c memory_probe_store(struct class *class,
Quoted 10 lines
drivers/base/memory.c +3
-1phys_addr =simple_strtoull (buf,NULL ,0 ); +if (phys_addr& ((pages_per_block<<PAGE_SHIFT ) -1 )) +return -EINVAL ; +for (i =0 ; i< sections_per_block; i++) { nid =memory_add_physaddr_to_nid (phys_addr); ret = add_memory(nid, phys_addr, --
what platform doese it affect? PowerPC or else?
As I know, on x86 platform it should not use this interface: *probe*, instead of acpi_hotplug_xxx. But PowerPC is RISC so how can you add such weird address for it? Maybe it is because PowerPC uses 16M as one section size and you assign a wrong address to it intentionally. The final result is as you show, isn't it?