[RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

STALE5050d

Revision v9 of 7 in this series.

61 messages, 6 authors, 2012-10-09 · open the first message on its own page

[RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: <hidden>
Date: 2012-09-05 09:24:42

From: Wen Congyang <redacted>

This patch series aims to support physical memory hot-remove.

The patches can free/remove the following things:

  - acpi_memory_info                          : [RFC PATCH 4/19]
  - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19]
  - iomem_resource                            : [RFC PATCH 9/19]
  - mem_section and related sysfs files       : [RFC PATCH 10-11, 13-16/19]
  - page table of removed memory              : [RFC PATCH 12/19]
  - node and related sysfs files              : [RFC PATCH 18-19/19]

If you find lack of function for physical memory hot-remove, please let me
know.

How to test this patchset?
1. apply this patchset and build the kernel. MEMORY_HOTPLUG, MEMORY_HOTREMOVE,
   ACPI_HOTPLUG_MEMORY must be selected.
2. load the module acpi_memhotplug
3. hotplug the memory device(it depends on your hardware)
   You will see the memory device under the directory /sys/bus/acpi/devices/.
   Its name is PNP0C80:XX.
4. online/offline pages provided by this memory device
   You can write online/offline to /sys/devices/system/memory/memoryX/state to
   online/offline pages provided by this memory device
5. hotremove the memory device
   You can hotremove the memory device by the hardware, or writing 1 to
   /sys/bus/acpi/devices/PNP0C80:XX/eject.

Note: if the memory provided by the memory device is used by the kernel, it
can't be offlined. It is not a bug.

Known problems:
1. memory can't be offlined when CONFIG_MEMCG is selected.
   For example: there is a memory device on node 1. The address range
   is [1G, 1.5G). You will find 4 new directories memory8, memory9, memory10,
   and memory11 under the directory /sys/devices/system/memory/.
   If CONFIG_MEMCG is selected, we will allocate memory to store page cgroup
   when we online pages. When we online memory8, the memory stored page cgroup
   is not provided by this memory device. But when we online memory9, the memory
   stored page cgroup may be provided by memory8. So we can't offline memory8
   now. We should offline the memory in the reversed order.
   When the memory device is hotremoved, we will auto offline memory provided
   by this memory device. But we don't know which memory is onlined first, so
   offlining memory may fail. In such case, you should offline the memory by
   hand before hotremoving the memory device.
2. hotremoving memory device may cause kernel panicked
   This bug will be fixed by Liu Jiang's patch:
   https://lkml.org/lkml/2012/7/3/1

change log of v9:
 [RFC PATCH v9 8/21]
   * add a lock to protect the list map_entries
   * add an indicator to firmware_map_entry to remember whether the memory
     is allocated from bootmem
 [RFC PATCH v9 10/21]
   * change the macro to inline function
 [RFC PATCH v9 19/21]
   * don't offline the node if the cpu on the node is onlined
 [RFC PATCH v9 21/21]
   * create new patch: auto offline page_cgroup when onlining memory block
     failed

change log of v8:
 [RFC PATCH v8 17/20]
   * Fix problems when one node's range include the other nodes
 [RFC PATCH v8 18/20]
   * fix building error when CONFIG_MEMORY_HOTPLUG_SPARSE or CONFIG_HUGETLBFS
     is not defined.
 [RFC PATCH v8 19/20]
   * don't offline node when some memory sections are not removed
 [RFC PATCH v8 20/20]
   * create new patch: clear hwpoisoned flag when onlining pages

change log of v7:
 [RFC PATCH v7 4/19]
   * do not continue if acpi_memory_device_remove_memory() fails.
 [RFC PATCH v7 15/19]
   * handle usemap in register_page_bootmem_info_section() too.

change log of v6:
 [RFC PATCH v6 12/19]
   * fix building error on other archtitectures than x86

 [RFC PATCH v6 15-16/19]
   * fix building error on other archtitectures than x86

change log of v5:
 * merge the patchset to clear page table and the patchset to hot remove
   memory(from ishimatsu) to one big patchset.

 [RFC PATCH v5 1/19]
   * rename remove_memory() to offline_memory()/offline_pages()

 [RFC PATCH v5 2/19]
   * new patch: implement offline_memory(). This function offlines pages,
     update memory block's state, and notify the userspace that the memory
     block's state is changed.

 [RFC PATCH v5 4/19]
   * offline and remove memory in acpi_memory_disable_device() too.

 [RFC PATCH v5 17/19]
   * new patch: add a new function __remove_zone() to revert the things done
     in the function __add_zone().

 [RFC PATCH v5 18/19]
   * flush work befor reseting node device.

change log of v4:
 * remove "memory-hotplug : unify argument of firmware_map_add_early/hotplug"
   from the patch series, since the patch is a bugfix. It is being disccussed
   on other thread. But for testing the patch series, the patch is needed.
   So I added the patch as [PATCH 0/13].

 [RFC PATCH v4 2/13]
   * check memory is online or not at remove_memory()
   * add memory_add_physaddr_to_nid() to acpi_memory_device_remove() for
     getting node id
 
 [RFC PATCH v4 3/13]
   * create new patch : check memory is online or not at online_pages()

 [RFC PATCH v4 4/13]
   * add __ref section to remove_memory()
   * call firmware_map_remove_entry() before remove_sysfs_fw_map_entry()

 [RFC PATCH v4 11/13]
   * rewrite register_page_bootmem_memmap() for removing page used as PT/PMD

change log of v3:
 * rebase to 3.5.0-rc6

 [RFC PATCH v2 2/13]
   * remove extra kobject_put()

   * The patch was commented by Wen. Wen's comment is
     "acpi_memory_device_remove() should ignore a return value of
     remove_memory() since caller does not care the return value".
     But I did not change it since I think caller should care the
     return value. And I am trying to fix it as follow:

     https://lkml.org/lkml/2012/7/5/624

 [RFC PATCH v2 4/13]
   * remove a firmware_memmap_entry allocated by kzmalloc()

change log of v2:
 [RFC PATCH v2 2/13]
   * check whether memory block is offline or not before calling offline_memory()
   * check whether section is valid or not in is_memblk_offline()
   * call kobject_put() for each memory_block in is_memblk_offline()

 [RFC PATCH v2 3/13]
   * unify the end argument of firmware_map_add_early/hotplug

 [RFC PATCH v2 4/13]
   * add release_firmware_map_entry() for freeing firmware_map_entry

 [RFC PATCH v2 6/13]
  * add release_memory_block() for freeing memory_block

 [RFC PATCH v2 11/13]
  * fix wrong arguments of free_pages()


Wen Congyang (8):
  memory-hotplug: implement offline_memory()
  memory-hotplug: store the node id in acpi_memory_device
  memory-hotplug: export the function acpi_bus_remove()
  memory-hotplug: call acpi_bus_remove() to remove memory device
  memory-hotplug: introduce new function arch_remove_memory()
  memory-hotplug: remove sysfs file of node
  memory-hotplug: clear hwpoisoned flag when onlining pages
  memory-hotplug: auto offline page_cgroup when onlining memory block
    failed

Yasuaki Ishimatsu (13):
  memory-hotplug: rename remove_memory() to
    offline_memory()/offline_pages()
  memory-hotplug: offline and remove memory when removing the memory
    device
  memory-hotplug: check whether memory is present or not
  memory-hotplug: remove /sys/firmware/memmap/X sysfs
  memory-hotplug: does not release memory region in PAGES_PER_SECTION
    chunks
  memory-hotplug: add memory_block_release
  memory-hotplug: remove_memory calls __remove_pages
  memory-hotplug: check page type in get_page_bootmem
  memory-hotplug: move register_page_bootmem_info_node and
    put_page_bootmem for sparse-vmemmap
  memory-hotplug: implement register_page_bootmem_info_section of
    sparse-vmemmap
  memory-hotplug: free memmap of sparse-vmemmap
  memory_hotplug: clear zone when the memory is removed
  memory-hotplug: add node_device_release

 arch/ia64/mm/discontig.c                        |   14 +
 arch/ia64/mm/init.c                             |   16 +
 arch/powerpc/mm/init_64.c                       |   14 +
 arch/powerpc/mm/mem.c                           |   14 +
 arch/powerpc/platforms/pseries/hotplug-memory.c |   16 +-
 arch/s390/mm/init.c                             |   12 +
 arch/s390/mm/vmem.c                             |   14 +
 arch/sh/mm/init.c                               |   15 +
 arch/sparc/mm/init_64.c                         |   14 +
 arch/tile/mm/init.c                             |    8 +
 arch/x86/include/asm/pgtable_types.h            |    1 +
 arch/x86/mm/init_32.c                           |   10 +
 arch/x86/mm/init_64.c                           |  331 ++++++++++++++++++
 arch/x86/mm/pageattr.c                          |   47 ++--
 drivers/acpi/acpi_memhotplug.c                  |   54 +++-
 drivers/acpi/scan.c                             |    3 +-
 drivers/base/memory.c                           |   88 ++++-
 drivers/base/node.c                             |   11 +
 drivers/firmware/memmap.c                       |   98 +++++-
 include/acpi/acpi_bus.h                         |    1 +
 include/linux/firmware-map.h                    |    6 +
 include/linux/memory.h                          |    5 +
 include/linux/memory_hotplug.h                  |   25 +-
 include/linux/mm.h                              |    5 +-
 include/linux/mmzone.h                          |   19 +
 mm/memory_hotplug.c                             |  424 +++++++++++++++++++++--
 mm/page_cgroup.c                                |    3 +
 mm/sparse.c                                     |    5 +-
 28 files changed, 1181 insertions(+), 92 deletions(-)

[RFC v9 PATCH 07/21] memory-hotplug: call acpi_bus_remove() to remove memory device

From: <hidden>
Date: 2012-09-05 09:20:33

From: Wen Congyang <redacted>

The memory device has been ejected and powoffed, so we can call
acpi_bus_remove() to remove the memory device from acpi bus.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 drivers/acpi/acpi_memhotplug.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 9d47458..b152767 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -425,8 +425,9 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
 		}
 
 		/*
-		 * TBD: Invoke acpi_bus_remove to cleanup data structures
+		 * Invoke acpi_bus_remove() to remove memory device
 		 */
+		acpi_bus_remove(device, 1);
 
 		/* _EJ0 succeeded; _OST is not necessary */
 		return;
-- 
1.7.1

[RFC v9 PATCH 03/21] memory-hotplug: store the node id in acpi_memory_device

From: <hidden>
Date: 2012-09-05 09:20:36

From: Wen Congyang <redacted>

The memory device has only one node id. Store the node id when
enable the memory device, and we can reuse it when removing the
memory device.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
Reviewed-by: Yasuaki Ishimatsu <redacted>
---
 drivers/acpi/acpi_memhotplug.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 2a7beac..7873832 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -83,6 +83,7 @@ struct acpi_memory_info {
 struct acpi_memory_device {
 	struct acpi_device * device;
 	unsigned int state;	/* State of the memory device */
+	int nid;
 	struct list_head res_list;
 };
 
@@ -256,6 +257,9 @@ static int acpi_memory_enable_device(struct acpi_memory_device *mem_device)
 		info->enabled = 1;
 		num_enabled++;
 	}
+
+	mem_device->nid = node;
+
 	if (!num_enabled) {
 		printk(KERN_ERR PREFIX "add_memory failed\n");
 		mem_device->state = MEMORY_INVALID_STATE;
-- 
1.7.1

[RFC v9 PATCH 06/21] memory-hotplug: export the function acpi_bus_remove()

From: <hidden>
Date: 2012-09-05 09:20:40

From: Wen Congyang <redacted>

The function acpi_bus_remove() can remove a acpi device from acpi device.
When a acpi device is removed, we need to call this function to remove
the acpi device from acpi bus. So export this function.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 drivers/acpi/scan.c     |    3 ++-
 include/acpi/acpi_bus.h |    1 +
 2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index d1ecca2..1cefc34 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -1224,7 +1224,7 @@ static int acpi_device_set_context(struct acpi_device *device)
 	return -ENODEV;
 }
 
-static int acpi_bus_remove(struct acpi_device *dev, int rmdevice)
+int acpi_bus_remove(struct acpi_device *dev, int rmdevice)
 {
 	if (!dev)
 		return -EINVAL;
@@ -1246,6 +1246,7 @@ static int acpi_bus_remove(struct acpi_device *dev, int rmdevice)
 
 	return 0;
 }
+EXPORT_SYMBOL(acpi_bus_remove);
 
 static int acpi_add_single_object(struct acpi_device **child,
 				  acpi_handle handle, int type,
diff --git a/include/acpi/acpi_bus.h b/include/acpi/acpi_bus.h
index bde976e..2ccf109 100644
--- a/include/acpi/acpi_bus.h
+++ b/include/acpi/acpi_bus.h
@@ -360,6 +360,7 @@ bool acpi_bus_power_manageable(acpi_handle handle);
 bool acpi_bus_can_wakeup(acpi_handle handle);
 int acpi_power_resource_register_device(struct device *dev, acpi_handle handle);
 void acpi_power_resource_unregister_device(struct device *dev, acpi_handle handle);
+int acpi_bus_remove(struct acpi_device *dev, int rmdevice);
 #ifdef CONFIG_ACPI_PROC_EVENT
 int acpi_bus_generate_proc_event(struct acpi_device *device, u8 type, int data);
 int acpi_bus_generate_proc_event4(const char *class, const char *bid, u8 type, int data);
-- 
1.7.1

[RFC v9 PATCH 08/21] memory-hotplug: remove /sys/firmware/memmap/X sysfs

From: <hidden>
Date: 2012-09-05 09:20:43

From: Yasuaki Ishimatsu <redacted>

When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
sysfs files are created. But there is no code to remove these files. The patch
implements the function to remove them.

Note : The code does not free firmware_map_entry since there is no way to free
       memory which is allocated by bootmem.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 drivers/firmware/memmap.c    |   98 +++++++++++++++++++++++++++++++++++++++++-
 include/linux/firmware-map.h |    6 +++
 mm/memory_hotplug.c          |    9 +++-
 3 files changed, 109 insertions(+), 4 deletions(-)
diff --git a/drivers/firmware/memmap.c b/drivers/firmware/memmap.c
index c1cdc92..6740d26 100644
--- a/drivers/firmware/memmap.c
+++ b/drivers/firmware/memmap.c
@@ -21,6 +21,7 @@
 #include <linux/types.h>
 #include <linux/bootmem.h>
 #include <linux/slab.h>
+#include <linux/mm.h>
 
 /*
  * Data types ------------------------------------------------------------------
@@ -41,6 +42,7 @@ struct firmware_map_entry {
 	const char		*type;	/* type of the memory range */
 	struct list_head	list;	/* entry for the linked list */
 	struct kobject		kobj;   /* kobject for each entry */
+	unsigned int		bootmem:1; /* allocated from bootmem */
 };
 
 /*
@@ -79,7 +81,26 @@ static const struct sysfs_ops memmap_attr_ops = {
 	.show = memmap_attr_show,
 };
 
+
+static inline struct firmware_map_entry *
+to_memmap_entry(struct kobject *kobj)
+{
+	return container_of(kobj, struct firmware_map_entry, kobj);
+}
+
+static void release_firmware_map_entry(struct kobject *kobj)
+{
+	struct firmware_map_entry *entry = to_memmap_entry(kobj);
+
+	if (entry->bootmem)
+		/* There is no way to free memory allocated from bootmem */
+		return;
+
+	kfree(entry);
+}
+
 static struct kobj_type memmap_ktype = {
+	.release	= release_firmware_map_entry,
 	.sysfs_ops	= &memmap_attr_ops,
 	.default_attrs	= def_attrs,
 };
@@ -94,6 +115,7 @@ static struct kobj_type memmap_ktype = {
  * in firmware initialisation code in one single thread of execution.
  */
 static LIST_HEAD(map_entries);
+static DEFINE_SPINLOCK(map_entries_lock);
 
 /**
  * firmware_map_add_entry() - Does the real work to add a firmware memmap entry.
@@ -118,11 +140,25 @@ static int firmware_map_add_entry(u64 start, u64 end,
 	INIT_LIST_HEAD(&entry->list);
 	kobject_init(&entry->kobj, &memmap_ktype);
 
+	spin_lock(&map_entries_lock);
 	list_add_tail(&entry->list, &map_entries);
+	spin_unlock(&map_entries_lock);
 
 	return 0;
 }
 
+/**
+ * firmware_map_remove_entry() - Does the real work to remove a firmware
+ * memmap entry.
+ * @entry: removed entry.
+ **/
+static inline void firmware_map_remove_entry(struct firmware_map_entry *entry)
+{
+	spin_lock(&map_entries_lock);
+	list_del(&entry->list);
+	spin_unlock(&map_entries_lock);
+}
+
 /*
  * Add memmap entry on sysfs
  */
@@ -144,6 +180,35 @@ static int add_sysfs_fw_map_entry(struct firmware_map_entry *entry)
 	return 0;
 }
 
+/*
+ * Remove memmap entry on sysfs
+ */
+static inline void remove_sysfs_fw_map_entry(struct firmware_map_entry *entry)
+{
+	kobject_put(&entry->kobj);
+}
+
+/*
+ * Search memmap entry
+ */
+
+static struct firmware_map_entry * __meminit
+firmware_map_find_entry(u64 start, u64 end, const char *type)
+{
+	struct firmware_map_entry *entry;
+
+	spin_lock(&map_entries_lock);
+	list_for_each_entry(entry, &map_entries, list)
+		if ((entry->start == start) && (entry->end == end) &&
+		    (!strcmp(entry->type, type))) {
+			spin_unlock(&map_entries_lock);
+			return entry;
+		}
+
+	spin_unlock(&map_entries_lock);
+	return NULL;
+}
+
 /**
  * firmware_map_add_hotplug() - Adds a firmware mapping entry when we do
  * memory hotplug.
@@ -193,9 +258,36 @@ int __init firmware_map_add_early(u64 start, u64 end, const char *type)
 	if (WARN_ON(!entry))
 		return -ENOMEM;
 
+	entry->bootmem = 1;
 	return firmware_map_add_entry(start, end, type, entry);
 }
 
+/**
+ * firmware_map_remove() - remove a firmware mapping entry
+ * @start: Start of the memory range.
+ * @end:   End of the memory range.
+ * @type:  Type of the memory range.
+ *
+ * removes a firmware mapping entry.
+ *
+ * Returns 0 on success, or -EINVAL if no entry.
+ **/
+int __meminit firmware_map_remove(u64 start, u64 end, const char *type)
+{
+	struct firmware_map_entry *entry;
+
+	entry = firmware_map_find_entry(start, end - 1, type);
+	if (!entry)
+		return -EINVAL;
+
+	firmware_map_remove_entry(entry);
+
+	/* remove the memmap entry */
+	remove_sysfs_fw_map_entry(entry);
+
+	return 0;
+}
+
 /*
  * Sysfs functions -------------------------------------------------------------
  */
@@ -217,8 +309,10 @@ static ssize_t type_show(struct firmware_map_entry *entry, char *buf)
 	return snprintf(buf, PAGE_SIZE, "%s\n", entry->type);
 }
 
-#define to_memmap_attr(_attr) container_of(_attr, struct memmap_attribute, attr)
-#define to_memmap_entry(obj) container_of(obj, struct firmware_map_entry, kobj)
+static inline struct memmap_attribute *to_memmap_attr(struct attribute *attr)
+{
+	return container_of(attr, struct memmap_attribute, attr);
+}
 
 static ssize_t memmap_attr_show(struct kobject *kobj,
 				struct attribute *attr, char *buf)
diff --git a/include/linux/firmware-map.h b/include/linux/firmware-map.h
index 43fe52f..71d4fa7 100644
--- a/include/linux/firmware-map.h
+++ b/include/linux/firmware-map.h
@@ -25,6 +25,7 @@
 
 int firmware_map_add_early(u64 start, u64 end, const char *type);
 int firmware_map_add_hotplug(u64 start, u64 end, const char *type);
+int firmware_map_remove(u64 start, u64 end, const char *type);
 
 #else /* CONFIG_FIRMWARE_MEMMAP */
 
@@ -38,6 +39,11 @@ static inline int firmware_map_add_hotplug(u64 start, u64 end, const char *type)
 	return 0;
 }
 
+static inline int firmware_map_remove(u64 start, u64 end, const char *type)
+{
+	return 0;
+}
+
 #endif /* CONFIG_FIRMWARE_MEMMAP */
 
 #endif /* _LINUX_FIRMWARE_MAP_H */
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 299747d..e74a01d 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -1052,9 +1052,9 @@ int offline_memory(u64 start, u64 size)
 	return 0;
 }
 
-int remove_memory(int nid, u64 start, u64 size)
+int __ref remove_memory(int nid, u64 start, u64 size)
 {
-	int ret = -EBUSY;
+	int ret = 0;
 	lock_memory_hotplug();
 	/*
 	 * The memory might become online by other task, even if you offine it.
@@ -1065,8 +1065,13 @@ int remove_memory(int nid, u64 start, u64 size)
 			"because the memmory range is online\n",
 			start, start + size);
 		ret = -EAGAIN;
+		goto out;
 	}
 
+	/* remove memmap entry */
+	firmware_map_remove(start, start + size, "System RAM");
+
+out:
 	unlock_memory_hotplug();
 	return ret;
 
-- 
1.7.1

[RFC v9 PATCH 21/21] memory-hotplug: auto offline page_cgroup when onlining memory block failed

From: <hidden>
Date: 2012-09-05 09:20:54

From: Wen Congyang <redacted>

When a memory block is onlined, we will try allocate memory on that node
to store page_cgroup. If onlining the memory block failed, we don't
offline the page cgroup, and we have no chance to offline this page cgroup
unless the memory block is onlined successfully again. It will cause
that we can't hot-remove the memory device on that node, because some
memory is used to store page cgroup. If onlining the memory block
is failed, there is no need to stort page cgroup for this memory. So
auto offline page_cgroup when onlining memory block failed.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 mm/page_cgroup.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/mm/page_cgroup.c b/mm/page_cgroup.c
index 5ddad0c..44db00e 100644
--- a/mm/page_cgroup.c
+++ b/mm/page_cgroup.c
@@ -251,6 +251,9 @@ static int __meminit page_cgroup_callback(struct notifier_block *self,
 				mn->nr_pages, mn->status_change_nid);
 		break;
 	case MEM_CANCEL_ONLINE:
+		offline_page_cgroup(mn->start_pfn,
+				mn->nr_pages, mn->status_change_nid);
+		break;
 	case MEM_GOING_OFFLINE:
 		break;
 	case MEM_ONLINE:
-- 
1.7.1

[RFC v9 PATCH 20/21] memory-hotplug: clear hwpoisoned flag when onlining pages

From: <hidden>
Date: 2012-09-05 09:21:11

From: Wen Congyang <redacted>

hwpoisoned may set when we offline a page by the sysfs interface
/sys/devices/system/memory/soft_offline_page or
/sys/devices/system/memory/hard_offline_page. If we don't clear
this flag when onlining pages, this page can't be freed, and will
not in free list. So we can't offline these pages again. So we
should clear this flag when onlining pages.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 mm/memory_hotplug.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 270c249..140c080 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -661,6 +661,11 @@ EXPORT_SYMBOL_GPL(__online_page_increment_counters);
 
 void __online_page_free(struct page *page)
 {
+#ifdef CONFIG_MEMORY_FAILURE
+	/* The page may be marked HWPoisoned by soft/hard offline page */
+	ClearPageHWPoison(page);
+#endif
+
 	ClearPageReserved(page);
 	init_page_count(page);
 	__free_page(page);
-- 
1.7.1

[RFC v9 PATCH 15/21] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap

From: <hidden>
Date: 2012-09-05 09:23:01

From: Yasuaki Ishimatsu <redacted>

For removing memmap region of sparse-vmemmap which is allocated bootmem,
memmap region of sparse-vmemmap needs to be registered by get_page_bootmem().
So the patch searches pages of virtual mapping and registers the pages by
get_page_bootmem().

Note: register_page_bootmem_memmap() is not implemented for ia64, ppc, s390,
and sparc.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 arch/ia64/mm/discontig.c       |    6 ++++
 arch/powerpc/mm/init_64.c      |    6 ++++
 arch/s390/mm/vmem.c            |    6 ++++
 arch/sparc/mm/init_64.c        |    6 ++++
 arch/x86/mm/init_64.c          |   52 ++++++++++++++++++++++++++++++++++++++++
 include/linux/memory_hotplug.h |    2 +
 include/linux/mm.h             |    3 +-
 mm/memory_hotplug.c            |   31 +++++++++++++++++++++--
 8 files changed, 108 insertions(+), 4 deletions(-)
diff --git a/arch/ia64/mm/discontig.c b/arch/ia64/mm/discontig.c
index c641333..33943db 100644
--- a/arch/ia64/mm/discontig.c
+++ b/arch/ia64/mm/discontig.c
@@ -822,4 +822,10 @@ int __meminit vmemmap_populate(struct page *start_page,
 {
 	return vmemmap_populate_basepages(start_page, size, node);
 }
+
+void register_page_bootmem_memmap(unsigned long section_nr,
+				  struct page *start_page, unsigned long size)
+{
+	/* TODO */
+}
 #endif
diff --git a/arch/powerpc/mm/init_64.c b/arch/powerpc/mm/init_64.c
index 620b7ac..3690c44 100644
--- a/arch/powerpc/mm/init_64.c
+++ b/arch/powerpc/mm/init_64.c
@@ -298,5 +298,11 @@ int __meminit vmemmap_populate(struct page *start_page,
 
 	return 0;
 }
+
+void register_page_bootmem_memmap(unsigned long section_nr,
+				  struct page *start_page, unsigned long size)
+{
+	/* TODO */
+}
 #endif /* CONFIG_SPARSEMEM_VMEMMAP */
 
diff --git a/arch/s390/mm/vmem.c b/arch/s390/mm/vmem.c
index 6f896e7..eda55cd 100644
--- a/arch/s390/mm/vmem.c
+++ b/arch/s390/mm/vmem.c
@@ -227,6 +227,12 @@ out:
 	return ret;
 }
 
+void register_page_bootmem_memmap(unsigned long section_nr,
+				  struct page *start_page, unsigned long size)
+{
+	/* TODO */
+}
+
 /*
  * Add memory segment to the segment list if it doesn't overlap with
  * an already present segment.
diff --git a/arch/sparc/mm/init_64.c b/arch/sparc/mm/init_64.c
index d58edf5..add1cc7 100644
--- a/arch/sparc/mm/init_64.c
+++ b/arch/sparc/mm/init_64.c
@@ -2077,6 +2077,12 @@ void __meminit vmemmap_populate_print_last(void)
 		node_start = 0;
 	}
 }
+
+void register_page_bootmem_memmap(unsigned long section_nr,
+				  struct page *start_page, unsigned long size)
+{
+	/* TODO */
+}
 #endif /* CONFIG_SPARSEMEM_VMEMMAP */
 
 static void prot_init_common(unsigned long page_none,
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index e0d88ba..0075592 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -1138,6 +1138,58 @@ vmemmap_populate(struct page *start_page, unsigned long size, int node)
 	return 0;
 }
 
+void register_page_bootmem_memmap(unsigned long section_nr,
+				  struct page *start_page, unsigned long size)
+{
+	unsigned long addr = (unsigned long)start_page;
+	unsigned long end = (unsigned long)(start_page + size);
+	unsigned long next;
+	pgd_t *pgd;
+	pud_t *pud;
+	pmd_t *pmd;
+
+	for (; addr < end; addr = next) {
+		pte_t *pte = NULL;
+
+		pgd = pgd_offset_k(addr);
+		if (pgd_none(*pgd)) {
+			next = (addr + PAGE_SIZE) & PAGE_MASK;
+			continue;
+		}
+		get_page_bootmem(section_nr, pgd_page(*pgd), MIX_SECTION_INFO);
+
+		pud = pud_offset(pgd, addr);
+		if (pud_none(*pud)) {
+			next = (addr + PAGE_SIZE) & PAGE_MASK;
+			continue;
+		}
+		get_page_bootmem(section_nr, pud_page(*pud), MIX_SECTION_INFO);
+
+		if (!cpu_has_pse) {
+			next = (addr + PAGE_SIZE) & PAGE_MASK;
+			pmd = pmd_offset(pud, addr);
+			if (pmd_none(*pmd))
+				continue;
+			get_page_bootmem(section_nr, pmd_page(*pmd),
+					 MIX_SECTION_INFO);
+
+			pte = pte_offset_kernel(pmd, addr);
+			if (pte_none(*pte))
+				continue;
+			get_page_bootmem(section_nr, pte_page(*pte),
+					 SECTION_INFO);
+		} else {
+			next = pmd_addr_end(addr, end);
+
+			pmd = pmd_offset(pud, addr);
+			if (pmd_none(*pmd))
+				continue;
+			get_page_bootmem(section_nr, pmd_page(*pmd),
+					 SECTION_INFO);
+		}
+	}
+}
+
 void __meminit vmemmap_populate_print_last(void)
 {
 	if (p_start) {
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index 1133e63..2d18235 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -164,6 +164,8 @@ static inline void arch_refresh_nodedata(int nid, pg_data_t *pgdat)
 
 extern void register_page_bootmem_info_node(struct pglist_data *pgdat);
 extern void put_page_bootmem(struct page *page);
+extern void get_page_bootmem(unsigned long ingo, struct page *page,
+			     unsigned long type);
 
 /*
  * Lock for memory hotplug guarantees 1) all callbacks for memory hotplug
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 311be90..c607913 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1618,7 +1618,8 @@ int vmemmap_populate_basepages(struct page *start_page,
 						unsigned long pages, int node);
 int vmemmap_populate(struct page *start_page, unsigned long pages, int node);
 void vmemmap_populate_print_last(void);
-
+void register_page_bootmem_memmap(unsigned long section_nr, struct page *map,
+				  unsigned long size);
 
 enum mf_flags {
 	MF_COUNT_INCREASED = 1 << 0,
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index df6857b..647a7f2 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -91,8 +91,8 @@ static void release_memory_resource(struct resource *res)
 }
 
 #ifdef CONFIG_MEMORY_HOTPLUG_SPARSE
-static void get_page_bootmem(unsigned long info,  struct page *page,
-			     unsigned long type)
+void get_page_bootmem(unsigned long info,  struct page *page,
+		      unsigned long type)
 {
 	unsigned long page_type;
 
@@ -164,8 +164,33 @@ static void register_page_bootmem_info_section(unsigned long start_pfn)
 
 }
 #else
-static inline void register_page_bootmem_info_section(unsigned long start_pfn)
+static void register_page_bootmem_info_section(unsigned long start_pfn)
 {
+	unsigned long *usemap, mapsize, section_nr, i;
+	struct mem_section *ms;
+	struct page *page, *memmap;
+
+	if (!pfn_valid(start_pfn))
+		return;
+
+	section_nr = pfn_to_section_nr(start_pfn);
+	ms = __nr_to_section(section_nr);
+
+	memmap = sparse_decode_mem_map(ms->section_mem_map, section_nr);
+
+	page = virt_to_page(memmap);
+	mapsize = sizeof(struct page) * PAGES_PER_SECTION;
+	mapsize = PAGE_ALIGN(mapsize) >> PAGE_SHIFT;
+
+	register_page_bootmem_memmap(section_nr, memmap, PAGES_PER_SECTION);
+
+	usemap = __nr_to_section(section_nr)->pageblock_flags;
+	page = virt_to_page(usemap);
+
+	mapsize = PAGE_ALIGN(usemap_size()) >> PAGE_SHIFT;
+
+	for (i = 0; i < mapsize; i++, page++)
+		get_page_bootmem(section_nr, page, MIX_SECTION_INFO);
 }
 #endif
 
-- 
1.7.1

[RFC v9 PATCH 02/21] memory-hotplug: implement offline_memory()

From: <hidden>
Date: 2012-09-05 09:23:35

From: Wen Congyang <redacted>

The function offline_memory() will be called when hot removing a
memory device. The memory device may contain more than one memory
block. If the memory block has been offlined, __offline_pages()
will fail. So we should try to offline one memory block at a
time.

If the memory block is offlined in offline_memory(), we also
update it's state, and notify the userspace that its state is
changed.

The function offline_memory() also check each memory block's
state. So there is no need to check the memory block's state
before calling offline_memory().

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
CC: Vasilis Liaskovitis <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 drivers/base/memory.c          |   31 +++++++++++++++++++++++++++----
 include/linux/memory_hotplug.h |    2 ++
 mm/memory_hotplug.c            |   37 ++++++++++++++++++++++++++++++++++++-
 3 files changed, 65 insertions(+), 5 deletions(-)
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index 44e7de6..86c8821 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -275,13 +275,11 @@ memory_block_action(unsigned long phys_index, unsigned long action)
 	return ret;
 }
 
-static int memory_block_change_state(struct memory_block *mem,
+static int __memory_block_change_state(struct memory_block *mem,
 		unsigned long to_state, unsigned long from_state_req)
 {
 	int ret = 0;
 
-	mutex_lock(&mem->state_mutex);
-
 	if (mem->state != from_state_req) {
 		ret = -EINVAL;
 		goto out;
@@ -309,10 +307,20 @@ static int memory_block_change_state(struct memory_block *mem,
 		break;
 	}
 out:
-	mutex_unlock(&mem->state_mutex);
 	return ret;
 }
 
+static int memory_block_change_state(struct memory_block *mem,
+		unsigned long to_state, unsigned long from_state_req)
+{
+	int ret;
+
+	mutex_lock(&mem->state_mutex);
+	ret = __memory_block_change_state(mem, to_state, from_state_req);
+	mutex_unlock(&mem->state_mutex);
+
+	return ret;
+}
 static ssize_t
 store_mem_state(struct device *dev,
 		struct device_attribute *attr, const char *buf, size_t count)
@@ -653,6 +661,21 @@ int unregister_memory_section(struct mem_section *section)
 }
 
 /*
+ * offline one memory block. If the memory block has been offlined, do nothing.
+ */
+int offline_memory_block(struct memory_block *mem)
+{
+	int ret = 0;
+
+	mutex_lock(&mem->state_mutex);
+	if (mem->state != MEM_OFFLINE)
+		ret = __memory_block_change_state(mem, MEM_OFFLINE, MEM_ONLINE);
+	mutex_unlock(&mem->state_mutex);
+
+	return ret;
+}
+
+/*
  * Initialize the sysfs support for memory devices...
  */
 int __init memory_dev_init(void)
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index c183f39..0b040bb 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -10,6 +10,7 @@ struct page;
 struct zone;
 struct pglist_data;
 struct mem_section;
+struct memory_block;
 
 #ifdef CONFIG_MEMORY_HOTPLUG
 
@@ -234,6 +235,7 @@ extern int mem_online_node(int nid);
 extern int add_memory(int nid, u64 start, u64 size);
 extern int arch_add_memory(int nid, u64 start, u64 size);
 extern int offline_pages(unsigned long start_pfn, unsigned long nr_pages);
+extern int offline_memory_block(struct memory_block *mem);
 extern int offline_memory(u64 start, u64 size);
 extern int sparse_add_one_section(struct zone *zone, unsigned long start_pfn,
 								int nr_pages);
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index bb42316..6fc1908 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -1001,7 +1001,42 @@ int offline_pages(unsigned long start_pfn, unsigned long nr_pages)
 
 int offline_memory(u64 start, u64 size)
 {
-	return -EINVAL;
+	struct memory_block *mem = NULL;
+	struct mem_section *section;
+	unsigned long start_pfn, end_pfn;
+	unsigned long pfn, section_nr;
+	int ret;
+
+	start_pfn = PFN_DOWN(start);
+	end_pfn = start_pfn + PFN_DOWN(size);
+
+	for (pfn = start_pfn; pfn < end_pfn; pfn += PAGES_PER_SECTION) {
+		section_nr = pfn_to_section_nr(pfn);
+		if (!present_section_nr(section_nr))
+			continue;
+
+		section = __nr_to_section(section_nr);
+		/* same memblock? */
+		if (mem)
+			if ((section_nr >= mem->start_section_nr) &&
+			    (section_nr <= mem->end_section_nr))
+				continue;
+
+		mem = find_memory_block_hinted(section, mem);
+		if (!mem)
+			continue;
+
+		ret = offline_memory_block(mem);
+		if (ret) {
+			kobject_put(&mem->dev.kobj);
+			return ret;
+		}
+	}
+
+	if (mem)
+		kobject_put(&mem->dev.kobj);
+
+	return 0;
 }
 #else
 int offline_pages(unsigned long start, unsigned long size)
-- 
1.7.1

[RFC v9 PATCH 05/21] memory-hotplug: check whether memory is present or not

From: <hidden>
Date: 2012-09-05 09:23:55

From: Yasuaki Ishimatsu <redacted>

If system supports memory hot-remove, online_pages() may online removed pages.
So online_pages() need to check whether onlining pages are present or not.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
 include/linux/mmzone.h |   19 +++++++++++++++++++
 mm/memory_hotplug.c    |   13 +++++++++++++
 2 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 2daa54f..ac3ae30 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -1180,6 +1180,25 @@ void sparse_init(void);
 #define sparse_index_init(_sec, _nid)  do {} while (0)
 #endif /* CONFIG_SPARSEMEM */
 
+#ifdef CONFIG_SPARSEMEM
+static inline int pfns_present(unsigned long pfn, unsigned long nr_pages)
+{
+	int i;
+	for (i = 0; i < nr_pages; i++) {
+		if (pfn_present(pfn + i))
+			continue;
+		else
+			return -EINVAL;
+	}
+	return 0;
+}
+#else
+static inline int pfns_present(unsigned long pfn, unsigned long nr_pages)
+{
+	return 0;
+}
+#endif /* CONFIG_SPARSEMEM*/
+
 #ifdef CONFIG_NODES_SPAN_OTHER_NODES
 bool early_pfn_in_nid(unsigned long pfn, int nid);
 #else
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 49f7747..299747d 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -467,6 +467,19 @@ int __ref online_pages(unsigned long pfn, unsigned long nr_pages)
 	struct memory_notify arg;
 
 	lock_memory_hotplug();
+	/*
+	 * If system supports memory hot-remove, the memory may have been
+	 * removed. So we check whether the memory has been removed or not.
+	 *
+	 * Note: When CONFIG_SPARSEMEM is defined, pfns_present() become
+	 *       effective. If CONFIG_SPARSEMEM is not defined, pfns_present()
+	 *       always returns 0.
+	 */
+	ret = pfns_present(pfn, nr_pages);
+	if (ret) {
+		unlock_memory_hotplug();
+		return ret;
+	}
 	arg.start_pfn = pfn;
 	arg.nr_pages = nr_pages;
 	arg.status_change_nid = -1;
-- 
1.7.1

[RFC v9 PATCH 04/21] memory-hotplug: offline and remove memory when removing the memory device

From: <hidden>
Date: 2012-09-05 09:23:56

From: Yasuaki Ishimatsu <redacted>

We should offline and remove memory when removing the memory device.
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject

In the 1st case, acpi_memory_disable_device() will be called. In the 2nd
case, acpi_memory_device_remove() will be called. acpi_memory_device_remove()
will also be called when we unbind the memory device from the driver
acpi_memhotplug. If the type is ACPI_BUS_REMOVAL_EJECT, it means
that the user wants to eject the memory device, and we should offline
and remove memory in acpi_memory_device_remove().

The function remove_memory() is not implemeted now. It only check whether
all memory has been offllined now.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 drivers/acpi/acpi_memhotplug.c |   45 +++++++++++++++++++++++++++++++++------
 drivers/base/memory.c          |   39 ++++++++++++++++++++++++++++++++++
 include/linux/memory.h         |    5 ++++
 include/linux/memory_hotplug.h |    5 ++++
 mm/memory_hotplug.c            |   22 +++++++++++++++++++
 5 files changed, 109 insertions(+), 7 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 7873832..9d47458 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -29,6 +29,7 @@
 #include <linux/module.h>
 #include <linux/init.h>
 #include <linux/types.h>
+#include <linux/memory.h>
 #include <linux/memory_hotplug.h>
 #include <linux/slab.h>
 #include <acpi/acpi_drivers.h>
@@ -310,25 +311,44 @@ static int acpi_memory_powerdown_device(struct acpi_memory_device *mem_device)
 	return 0;
 }
 
-static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
+static int
+acpi_memory_device_remove_memory(struct acpi_memory_device *mem_device)
 {
 	int result;
 	struct acpi_memory_info *info, *n;
+	int node = mem_device->nid;
 
-
-	/*
-	 * Ask the VM to offline this memory range.
-	 * Note: Assume that this function returns zero on success
-	 */
 	list_for_each_entry_safe(info, n, &mem_device->res_list, list) {
 		if (info->enabled) {
 			result = offline_memory(info->start_addr, info->length);
 			if (result)
 				return result;
+
+			result = remove_memory(node, info->start_addr,
+					       info->length);
+			if (result)
+				return result;
 		}
+
+		list_del(&info->list);
 		kfree(info);
 	}
 
+	return 0;
+}
+
+static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
+{
+	int result;
+
+	/*
+	 * Ask the VM to offline this memory range.
+	 * Note: Assume that this function returns zero on success
+	 */
+	result = acpi_memory_device_remove_memory(mem_device);
+	if (result)
+		return result;
+
 	/* Power-off and eject the device */
 	result = acpi_memory_powerdown_device(mem_device);
 	if (result) {
@@ -477,12 +497,23 @@ static int acpi_memory_device_add(struct acpi_device *device)
 static int acpi_memory_device_remove(struct acpi_device *device, int type)
 {
 	struct acpi_memory_device *mem_device = NULL;
-
+	int result;
 
 	if (!device || !acpi_driver_data(device))
 		return -EINVAL;
 
 	mem_device = acpi_driver_data(device);
+
+	if (type == ACPI_BUS_REMOVAL_EJECT) {
+		/*
+		 * offline and remove memory only when the memory device is
+		 * ejected.
+		 */
+		result = acpi_memory_device_remove_memory(mem_device);
+		if (result)
+			return result;
+	}
+
 	kfree(mem_device);
 
 	return 0;
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index 86c8821..038be73 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -70,6 +70,45 @@ void unregister_memory_isolate_notifier(struct notifier_block *nb)
 }
 EXPORT_SYMBOL(unregister_memory_isolate_notifier);
 
+bool is_memblk_offline(unsigned long start, unsigned long size)
+{
+	struct memory_block *mem = NULL;
+	struct mem_section *section;
+	unsigned long start_pfn, end_pfn;
+	unsigned long pfn, section_nr;
+
+	start_pfn = PFN_DOWN(start);
+	end_pfn = PFN_UP(start + size);
+
+	for (pfn = start_pfn; pfn < end_pfn; pfn += PAGES_PER_SECTION) {
+		section_nr = pfn_to_section_nr(pfn);
+		if (!present_section_nr(section_nr))
+			continue;
+
+		section = __nr_to_section(section_nr);
+		/* same memblock? */
+		if (mem)
+			if ((section_nr >= mem->start_section_nr) &&
+			    (section_nr <= mem->end_section_nr))
+				continue;
+
+		mem = find_memory_block_hinted(section, mem);
+		if (!mem)
+			continue;
+		if (mem->state == MEM_OFFLINE)
+			continue;
+
+		kobject_put(&mem->dev.kobj);
+		return false;
+	}
+
+	if (mem)
+		kobject_put(&mem->dev.kobj);
+
+	return true;
+}
+EXPORT_SYMBOL(is_memblk_offline);
+
 /*
  * register_memory - Setup a sysfs device for a memory block
  */
diff --git a/include/linux/memory.h b/include/linux/memory.h
index 1ac7f6e..7c66126 100644
--- a/include/linux/memory.h
+++ b/include/linux/memory.h
@@ -106,6 +106,10 @@ static inline int memory_isolate_notify(unsigned long val, void *v)
 {
 	return 0;
 }
+static inline bool is_memblk_offline(unsigned long start, unsigned long size)
+{
+	return false;
+}
 #else
 extern int register_memory_notifier(struct notifier_block *nb);
 extern void unregister_memory_notifier(struct notifier_block *nb);
@@ -120,6 +124,7 @@ extern int memory_isolate_notify(unsigned long val, void *v);
 extern struct memory_block *find_memory_block_hinted(struct mem_section *,
 							struct memory_block *);
 extern struct memory_block *find_memory_block(struct mem_section *);
+extern bool is_memblk_offline(unsigned long start, unsigned long size);
 #define CONFIG_MEM_BLOCK_SIZE	(PAGES_PER_SECTION<<PAGE_SHIFT)
 enum mem_add_context { BOOT, HOTPLUG };
 #endif /* CONFIG_MEMORY_HOTPLUG_SPARSE */
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index 0b040bb..fd84ea9 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -222,6 +222,7 @@ static inline void unlock_memory_hotplug(void) {}
 #ifdef CONFIG_MEMORY_HOTREMOVE
 
 extern int is_mem_section_removable(unsigned long pfn, unsigned long nr_pages);
+extern int remove_memory(int nid, u64 start, u64 size);
 
 #else
 static inline int is_mem_section_removable(unsigned long pfn,
@@ -229,6 +230,10 @@ static inline int is_mem_section_removable(unsigned long pfn,
 {
 	return 0;
 }
+static inline int remove_memory(int nid, u64 start, u64 size)
+{
+	return -EBUSY;
+}
 #endif /* CONFIG_MEMORY_HOTREMOVE */
 
 extern int mem_online_node(int nid);
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 6fc1908..49f7747 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -1038,6 +1038,28 @@ int offline_memory(u64 start, u64 size)
 
 	return 0;
 }
+
+int remove_memory(int nid, u64 start, u64 size)
+{
+	int ret = -EBUSY;
+	lock_memory_hotplug();
+	/*
+	 * The memory might become online by other task, even if you offine it.
+	 * So we check whether the memory has been onlined or not.
+	 */
+	if (!is_memblk_offline(start, size)) {
+		pr_warn("memory removing [mem %#010llx-%#010llx] failed, "
+			"because the memmory range is online\n",
+			start, start + size);
+		ret = -EAGAIN;
+	}
+
+	unlock_memory_hotplug();
+	return ret;
+
+}
+EXPORT_SYMBOL_GPL(remove_memory);
+
 #else
 int offline_pages(unsigned long start, unsigned long size)
 {
-- 
1.7.1

[RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages()

From: <hidden>
Date: 2012-09-05 09:24:43

From: Yasuaki Ishimatsu <redacted>

remove_memory() only try to offline pages. It is called in two cases:
1. hot remove a memory device
2. echo offline >/sys/devices/system/memory/memoryXX/state

In the 1st case, we should also change memory block's state, and notify
the userspace that the memory block's state is changed after offlining
pages.

So rename remove_memory() to offline_memory()/offline_pages(). And in
the 1st case, offline_memory() will be used. The function offline_memory()
is not implemented. In the 2nd case, offline_pages() will be used.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 drivers/acpi/acpi_memhotplug.c |    2 +-
 drivers/base/memory.c          |    9 +++------
 include/linux/memory_hotplug.h |    3 ++-
 mm/memory_hotplug.c            |   22 ++++++++++++++--------
 4 files changed, 20 insertions(+), 16 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 24c807f..2a7beac 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -318,7 +318,7 @@ static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
 	 */
 	list_for_each_entry_safe(info, n, &mem_device->res_list, list) {
 		if (info->enabled) {
-			result = remove_memory(info->start_addr, info->length);
+			result = offline_memory(info->start_addr, info->length);
 			if (result)
 				return result;
 		}
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index 7dda4f7..44e7de6 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -248,26 +248,23 @@ static bool pages_correctly_reserved(unsigned long start_pfn,
 static int
 memory_block_action(unsigned long phys_index, unsigned long action)
 {
-	unsigned long start_pfn, start_paddr;
+	unsigned long start_pfn;
 	unsigned long nr_pages = PAGES_PER_SECTION * sections_per_block;
 	struct page *first_page;
 	int ret;
 
 	first_page = pfn_to_page(phys_index << PFN_SECTION_SHIFT);
+	start_pfn = page_to_pfn(first_page);
 
 	switch (action) {
 		case MEM_ONLINE:
-			start_pfn = page_to_pfn(first_page);
-
 			if (!pages_correctly_reserved(start_pfn, nr_pages))
 				return -EBUSY;
 
 			ret = online_pages(start_pfn, nr_pages);
 			break;
 		case MEM_OFFLINE:
-			start_paddr = page_to_pfn(first_page) << PAGE_SHIFT;
-			ret = remove_memory(start_paddr,
-					    nr_pages << PAGE_SHIFT);
+			ret = offline_pages(start_pfn, nr_pages);
 			break;
 		default:
 			WARN(1, KERN_WARNING "%s(%ld, %ld) unknown action: "
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index 910550f..c183f39 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -233,7 +233,8 @@ static inline int is_mem_section_removable(unsigned long pfn,
 extern int mem_online_node(int nid);
 extern int add_memory(int nid, u64 start, u64 size);
 extern int arch_add_memory(int nid, u64 start, u64 size);
-extern int remove_memory(u64 start, u64 size);
+extern int offline_pages(unsigned long start_pfn, unsigned long nr_pages);
+extern int offline_memory(u64 start, u64 size);
 extern int sparse_add_one_section(struct zone *zone, unsigned long start_pfn,
 								int nr_pages);
 extern void sparse_remove_one_section(struct zone *zone, struct mem_section *ms);
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 3ad25f9..bb42316 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -866,7 +866,7 @@ check_pages_isolated(unsigned long start_pfn, unsigned long end_pfn)
 	return offlined;
 }
 
-static int __ref offline_pages(unsigned long start_pfn,
+static int __ref __offline_pages(unsigned long start_pfn,
 		  unsigned long end_pfn, unsigned long timeout)
 {
 	unsigned long pfn, nr_pages, expire;
@@ -994,18 +994,24 @@ out:
 	return ret;
 }
 
-int remove_memory(u64 start, u64 size)
+int offline_pages(unsigned long start_pfn, unsigned long nr_pages)
 {
-	unsigned long start_pfn, end_pfn;
+	return __offline_pages(start_pfn, start_pfn + nr_pages, 120 * HZ);
+}
 
-	start_pfn = PFN_DOWN(start);
-	end_pfn = start_pfn + PFN_DOWN(size);
-	return offline_pages(start_pfn, end_pfn, 120 * HZ);
+int offline_memory(u64 start, u64 size)
+{
+	return -EINVAL;
 }
 #else
-int remove_memory(u64 start, u64 size)
+int offline_pages(unsigned long start, unsigned long size)
+{
+	return -EINVAL;
+}
+
+int offline_memory(u64 start, u64 size)
 {
 	return -EINVAL;
 }
 #endif /* CONFIG_MEMORY_HOTREMOVE */
-EXPORT_SYMBOL_GPL(remove_memory);
+EXPORT_SYMBOL_GPL(offline_memory);
-- 
1.7.1

[RFC v9 PATCH 09/21] memory-hotplug: does not release memory region in PAGES_PER_SECTION chunks

From: <hidden>
Date: 2012-09-05 09:25:32

From: Yasuaki Ishimatsu <redacted>

Since applying a patch(de7f0cba96786c), release_mem_region() has been changed
as called in PAGES_PER_SECTION chunks because register_memory_resource() is
called in PAGES_PER_SECTION chunks by add_memory(). But it seems firmware
dependency. If CRS are written in the PAGES_PER_SECTION chunks in ACPI DSDT
Table, register_memory_resource() is called in PAGES_PER_SECTION chunks.
But if CRS are written in the DIMM unit in ACPI DSDT Table,
register_memory_resource() is called in DIMM unit. So release_mem_region()
should not be called in PAGES_PER_SECTION chunks. The patch fixes it.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
 arch/powerpc/platforms/pseries/hotplug-memory.c |   13 +++++++++----
 mm/memory_hotplug.c                             |    4 ++--
 2 files changed, 11 insertions(+), 6 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/hotplug-memory.c b/arch/powerpc/platforms/pseries/hotplug-memory.c
index 11d8e05..dc0a035 100644
--- a/arch/powerpc/platforms/pseries/hotplug-memory.c
+++ b/arch/powerpc/platforms/pseries/hotplug-memory.c
@@ -77,7 +77,8 @@ static int pseries_remove_memblock(unsigned long base, unsigned int memblock_siz
 {
 	unsigned long start, start_pfn;
 	struct zone *zone;
-	int ret;
+	int i, ret;
+	int sections_to_remove;
 
 	start_pfn = base >> PAGE_SHIFT;
 
@@ -97,9 +98,13 @@ static int pseries_remove_memblock(unsigned long base, unsigned int memblock_siz
 	 * to sysfs "state" file and we can't remove sysfs entries
 	 * while writing to it. So we have to defer it to here.
 	 */
-	ret = __remove_pages(zone, start_pfn, memblock_size >> PAGE_SHIFT);
-	if (ret)
-		return ret;
+	sections_to_remove = (memblock_size >> PAGE_SHIFT) / PAGES_PER_SECTION;
+	for (i = 0; i < sections_to_remove; i++) {
+		unsigned long pfn = start_pfn + i * PAGES_PER_SECTION;
+		ret = __remove_pages(zone, start_pfn,  PAGES_PER_SECTION);
+		if (ret)
+			return ret;
+	}
 
 	/*
 	 * Update memory regions for memory remove
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index e74a01d..2353887 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -358,11 +358,11 @@ int __remove_pages(struct zone *zone, unsigned long phys_start_pfn,
 	BUG_ON(phys_start_pfn & ~PAGE_SECTION_MASK);
 	BUG_ON(nr_pages % PAGES_PER_SECTION);
 
+	release_mem_region(phys_start_pfn << PAGE_SHIFT,  nr_pages * PAGE_SIZE);
+
 	sections_to_remove = nr_pages / PAGES_PER_SECTION;
 	for (i = 0; i < sections_to_remove; i++) {
 		unsigned long pfn = phys_start_pfn + i*PAGES_PER_SECTION;
-		release_mem_region(pfn << PAGE_SHIFT,
-				   PAGES_PER_SECTION << PAGE_SHIFT);
 		ret = __remove_section(zone, __pfn_to_section(pfn));
 		if (ret)
 			break;
-- 
1.7.1

[RFC v9 PATCH 13/21] memory-hotplug: check page type in get_page_bootmem

From: <hidden>
Date: 2012-09-05 09:45:01

From: Yasuaki Ishimatsu <redacted>

The function get_page_bootmem() may be called more than one time to the same
page. There is no need to set page's type, private if the function is not
the first time called to the page.

Note: the patch is just optimization and does not fix any problem.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
 mm/memory_hotplug.c |   15 +++++++++++----
 1 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index d736df3..26a5012 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -95,10 +95,17 @@ static void release_memory_resource(struct resource *res)
 static void get_page_bootmem(unsigned long info,  struct page *page,
 			     unsigned long type)
 {
-	page->lru.next = (struct list_head *) type;
-	SetPagePrivate(page);
-	set_page_private(page, info);
-	atomic_inc(&page->_count);
+	unsigned long page_type;
+
+	page_type = (unsigned long)page->lru.next;
+	if (page_type < MEMORY_HOTPLUG_MIN_BOOTMEM_TYPE ||
+	    page_type > MEMORY_HOTPLUG_MAX_BOOTMEM_TYPE){
+		page->lru.next = (struct list_head *)type;
+		SetPagePrivate(page);
+		set_page_private(page, info);
+		atomic_inc(&page->_count);
+	} else
+		atomic_inc(&page->_count);
 }
 
 /* reference to __meminit __free_pages_bootmem is valid
-- 
1.7.1

[RFC v9 PATCH 10/21] memory-hotplug: add memory_block_release

From: <hidden>
Date: 2012-09-05 09:45:04

From: Yasuaki Ishimatsu <redacted>

When calling remove_memory_block(), the function shows following message at
device_release().

Device 'memory528' does not have a release() function, it is broken and must
be fixed.

remove_memory_block() calls kfree(mem). I think it shouled be called from
device_release(). So the patch implements memory_block_release()

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
 drivers/base/memory.c |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index 038be73..f44d624 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -109,6 +109,13 @@ bool is_memblk_offline(unsigned long start, unsigned long size)
 }
 EXPORT_SYMBOL(is_memblk_offline);
 
+static void release_memory_block(struct device *dev)
+{
+	struct memory_block *mem = container_of(dev, struct memory_block, dev);
+
+	kfree(mem);
+}
+
 /*
  * register_memory - Setup a sysfs device for a memory block
  */
@@ -119,6 +126,7 @@ int register_memory(struct memory_block *memory)
 
 	memory->dev.bus = &memory_subsys;
 	memory->dev.id = memory->start_section_nr / sections_per_block;
+	memory->dev.release = release_memory_block;
 
 	error = device_register(&memory->dev);
 	return error;
@@ -674,7 +682,6 @@ int remove_memory_block(unsigned long node_id, struct mem_section *section,
 		mem_remove_simple_file(mem, phys_device);
 		mem_remove_simple_file(mem, removable);
 		unregister_memory(mem);
-		kfree(mem);
 	} else
 		kobject_put(&mem->dev.kobj);
 
-- 
1.7.1

[RFC v9 PATCH 19/21] memory-hotplug: remove sysfs file of node

From: <hidden>
Date: 2012-09-05 09:45:08

From: Wen Congyang <redacted>

This patch introduces a new function try_offline_node() to
remove sysfs file of node when all memory sections of this
node are removed. If some memory sections of this node are
not removed, this function does nothing.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 mm/memory_hotplug.c |   54 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 54 insertions(+), 0 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index afda7e9..270c249 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -29,6 +29,7 @@
 #include <linux/suspend.h>
 #include <linux/mm_inline.h>
 #include <linux/firmware-map.h>
+#include <linux/stop_machine.h>
 
 #include <asm/tlbflush.h>
 
@@ -1285,6 +1286,57 @@ int offline_memory(u64 start, u64 size)
 	return 0;
 }
 
+static int check_cpu_on_node(void *data)
+{
+	struct pglist_data *pgdat = data;
+	int cpu;
+
+	for_each_online_cpu(cpu) {
+		if (cpu_to_node(cpu) == pgdat->node_id)
+			/*
+			 * the cpu on this node is onlined, and we can't
+			 * offline this node.
+			 */
+			return -EBUSY;
+	}
+
+	return 0;
+}
+
+/* offline the node if all memory sections of this node are removed */
+static void try_offline_node(int nid)
+{
+	unsigned long start_pfn = NODE_DATA(nid)->node_start_pfn;
+	unsigned long end_pfn = start_pfn + NODE_DATA(nid)->node_spanned_pages;
+	unsigned long pfn;
+
+	for (pfn = start_pfn; pfn < end_pfn; pfn += PAGES_PER_SECTION) {
+		unsigned long section_nr = pfn_to_section_nr(pfn);
+
+		if (!present_section_nr(section_nr))
+			continue;
+
+		if (pfn_to_nid(pfn) != nid)
+			continue;
+
+		/*
+		 * some memory sections of this node are not removed, and we
+		 * can't offline node now.
+		 */
+		return;
+	}
+
+	if (stop_machine(check_cpu_on_node, NODE_DATA(nid), NULL))
+		return;
+
+	/*
+	 * all memory sections of this node are removed, we can offline this
+	 * node now.
+	 */
+	node_set_offline(nid);
+	unregister_one_node(nid);
+}
+
 int __ref remove_memory(int nid, u64 start, u64 size)
 {
 	int ret = 0;
@@ -1305,6 +1357,8 @@ int __ref remove_memory(int nid, u64 start, u64 size)
 	firmware_map_remove(start, start + size, "System RAM");
 
 	arch_remove_memory(start, size);
+
+	try_offline_node(nid);
 out:
 	unlock_memory_hotplug();
 	return ret;
-- 
1.7.1

[RFC v9 PATCH 14/21] memory-hotplug: move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap

From: <hidden>
Date: 2012-09-05 09:45:09

From: Yasuaki Ishimatsu <redacted>

For implementing register_page_bootmem_info_node of sparse-vmemmap,
register_page_bootmem_info_node and put_page_bootmem are moved to
memory_hotplug.c

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
 include/linux/memory_hotplug.h |    9 ---------
 mm/memory_hotplug.c            |    8 ++++++--
 2 files changed, 6 insertions(+), 11 deletions(-)
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index cdbbd79..1133e63 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -162,17 +162,8 @@ static inline void arch_refresh_nodedata(int nid, pg_data_t *pgdat)
 #endif /* CONFIG_NUMA */
 #endif /* CONFIG_HAVE_ARCH_NODEDATA_EXTENSION */
 
-#ifdef CONFIG_SPARSEMEM_VMEMMAP
-static inline void register_page_bootmem_info_node(struct pglist_data *pgdat)
-{
-}
-static inline void put_page_bootmem(struct page *page)
-{
-}
-#else
 extern void register_page_bootmem_info_node(struct pglist_data *pgdat);
 extern void put_page_bootmem(struct page *page);
-#endif
 
 /*
  * Lock for memory hotplug guarantees 1) all callbacks for memory hotplug
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 26a5012..df6857b 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -91,7 +91,6 @@ static void release_memory_resource(struct resource *res)
 }
 
 #ifdef CONFIG_MEMORY_HOTPLUG_SPARSE
-#ifndef CONFIG_SPARSEMEM_VMEMMAP
 static void get_page_bootmem(unsigned long info,  struct page *page,
 			     unsigned long type)
 {
@@ -127,6 +126,7 @@ void __ref put_page_bootmem(struct page *page)
 
 }
 
+#ifndef CONFIG_SPARSEMEM_VMEMMAP
 static void register_page_bootmem_info_section(unsigned long start_pfn)
 {
 	unsigned long *usemap, mapsize, section_nr, i;
@@ -163,6 +163,11 @@ static void register_page_bootmem_info_section(unsigned long start_pfn)
 		get_page_bootmem(section_nr, page, MIX_SECTION_INFO);
 
 }
+#else
+static inline void register_page_bootmem_info_section(unsigned long start_pfn)
+{
+}
+#endif
 
 void register_page_bootmem_info_node(struct pglist_data *pgdat)
 {
@@ -198,7 +203,6 @@ void register_page_bootmem_info_node(struct pglist_data *pgdat)
 		register_page_bootmem_info_section(pfn);
 
 }
-#endif /* !CONFIG_SPARSEMEM_VMEMMAP */
 
 static void grow_zone_span(struct zone *zone, unsigned long start_pfn,
 			   unsigned long end_pfn)
-- 
1.7.1

[RFC v9 PATCH 11/21] memory-hotplug: remove_memory calls __remove_pages

From: <hidden>
Date: 2012-09-05 09:45:11

From: Yasuaki Ishimatsu <redacted>

The patch adds __remove_pages() to remove_memory(). Then the range of
phys_start_pfn argument and nr_pages argument in __remove_pagse() may
have different zone. So zone argument is removed from __remove_pages()
and __remove_pages() caluculates zone in each section.

When CONFIG_SPARSEMEM_VMEMMAP is defined, there is no way to remove a memmap.
So __remove_section only calls unregister_memory_section().

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
 arch/powerpc/platforms/pseries/hotplug-memory.c |    5 +----
 include/linux/memory_hotplug.h                  |    3 +--
 mm/memory_hotplug.c                             |   17 ++++++++++-------
 3 files changed, 12 insertions(+), 13 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/hotplug-memory.c b/arch/powerpc/platforms/pseries/hotplug-memory.c
index dc0a035..cc14da4 100644
--- a/arch/powerpc/platforms/pseries/hotplug-memory.c
+++ b/arch/powerpc/platforms/pseries/hotplug-memory.c
@@ -76,7 +76,6 @@ unsigned long memory_block_size_bytes(void)
 static int pseries_remove_memblock(unsigned long base, unsigned int memblock_size)
 {
 	unsigned long start, start_pfn;
-	struct zone *zone;
 	int i, ret;
 	int sections_to_remove;
 
@@ -87,8 +86,6 @@ static int pseries_remove_memblock(unsigned long base, unsigned int memblock_siz
 		return 0;
 	}
 
-	zone = page_zone(pfn_to_page(start_pfn));
-
 	/*
 	 * Remove section mappings and sysfs entries for the
 	 * section of the memory we are removing.
@@ -101,7 +98,7 @@ static int pseries_remove_memblock(unsigned long base, unsigned int memblock_siz
 	sections_to_remove = (memblock_size >> PAGE_SHIFT) / PAGES_PER_SECTION;
 	for (i = 0; i < sections_to_remove; i++) {
 		unsigned long pfn = start_pfn + i * PAGES_PER_SECTION;
-		ret = __remove_pages(zone, start_pfn,  PAGES_PER_SECTION);
+		ret = __remove_pages(start_pfn,  PAGES_PER_SECTION);
 		if (ret)
 			return ret;
 	}
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index fd84ea9..8bf820d 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -90,8 +90,7 @@ extern bool is_pageblock_removable_nolock(struct page *page);
 /* reasonably generic interface to expand the physical pages in a zone  */
 extern int __add_pages(int nid, struct zone *zone, unsigned long start_pfn,
 	unsigned long nr_pages);
-extern int __remove_pages(struct zone *zone, unsigned long start_pfn,
-	unsigned long nr_pages);
+extern int __remove_pages(unsigned long start_pfn, unsigned long nr_pages);
 
 #ifdef CONFIG_NUMA
 extern int memory_add_physaddr_to_nid(u64 start);
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 2353887..7fbfc9f 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -275,11 +275,14 @@ static int __meminit __add_section(int nid, struct zone *zone,
 #ifdef CONFIG_SPARSEMEM_VMEMMAP
 static int __remove_section(struct zone *zone, struct mem_section *ms)
 {
-	/*
-	 * XXX: Freeing memmap with vmemmap is not implement yet.
-	 *      This should be removed later.
-	 */
-	return -EBUSY;
+	int ret = -EINVAL;
+
+	if (!valid_section(ms))
+		return ret;
+
+	ret = unregister_memory_section(ms);
+
+	return ret;
 }
 #else
 static int __remove_section(struct zone *zone, struct mem_section *ms)
@@ -346,8 +349,7 @@ EXPORT_SYMBOL_GPL(__add_pages);
  * sure that pages are marked reserved and zones are adjust properly by
  * calling offline_pages().
  */
-int __remove_pages(struct zone *zone, unsigned long phys_start_pfn,
-		 unsigned long nr_pages)
+int __remove_pages(unsigned long phys_start_pfn, unsigned long nr_pages)
 {
 	unsigned long i, ret = 0;
 	int sections_to_remove;
@@ -363,6 +365,7 @@ int __remove_pages(struct zone *zone, unsigned long phys_start_pfn,
 	sections_to_remove = nr_pages / PAGES_PER_SECTION;
 	for (i = 0; i < sections_to_remove; i++) {
 		unsigned long pfn = phys_start_pfn + i*PAGES_PER_SECTION;
+		struct zone *zone = page_zone(pfn_to_page(pfn));
 		ret = __remove_section(zone, __pfn_to_section(pfn));
 		if (ret)
 			break;
-- 
1.7.1

[RFC v9 PATCH 12/21] memory-hotplug: introduce new function arch_remove_memory()

From: <hidden>
Date: 2012-09-05 09:46:44

From: Wen Congyang <redacted>

We don't call __add_pages() directly in the function add_memory()
because some other architecture related things need to be done
before or after calling __add_pages(). So we should introduce
a new function arch_remove_memory() to revert the things
done in arch_add_memory().

Note: the function for s390 is not implemented(I don't know how to
implement it for s390).

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 arch/ia64/mm/init.c                  |   16 ++++
 arch/powerpc/mm/mem.c                |   14 +++
 arch/s390/mm/init.c                  |   12 +++
 arch/sh/mm/init.c                    |   15 +++
 arch/tile/mm/init.c                  |    8 ++
 arch/x86/include/asm/pgtable_types.h |    1 +
 arch/x86/mm/init_32.c                |   10 ++
 arch/x86/mm/init_64.c                |  160 ++++++++++++++++++++++++++++++++++
 arch/x86/mm/pageattr.c               |   47 +++++-----
 include/linux/memory_hotplug.h       |    1 +
 mm/memory_hotplug.c                  |    1 +
 11 files changed, 263 insertions(+), 22 deletions(-)
diff --git a/arch/ia64/mm/init.c b/arch/ia64/mm/init.c
index 0eab454..1e345ed 100644
--- a/arch/ia64/mm/init.c
+++ b/arch/ia64/mm/init.c
@@ -688,6 +688,22 @@ int arch_add_memory(int nid, u64 start, u64 size)
 
 	return ret;
 }
+
+#ifdef CONFIG_MEMORY_HOTREMOVE
+int arch_remove_memory(u64 start, u64 size)
+{
+	unsigned long start_pfn = start >> PAGE_SHIFT;
+	unsigned long nr_pages = size >> PAGE_SHIFT;
+	int ret;
+
+	ret = __remove_pages(start_pfn, nr_pages);
+	if (ret)
+		pr_warn("%s: Problem encountered in __remove_pages() as"
+			" ret=%d\n", __func__,  ret);
+
+	return ret;
+}
+#endif
 #endif
 
 /*
diff --git a/arch/powerpc/mm/mem.c b/arch/powerpc/mm/mem.c
index fbdad0e..011170b 100644
--- a/arch/powerpc/mm/mem.c
+++ b/arch/powerpc/mm/mem.c
@@ -133,6 +133,20 @@ int arch_add_memory(int nid, u64 start, u64 size)
 
 	return __add_pages(nid, zone, start_pfn, nr_pages);
 }
+
+#ifdef CONFIG_MEMORY_HOTREMOVE
+int arch_remove_memory(u64 start, u64 size)
+{
+	unsigned long start_pfn = start >> PAGE_SHIFT;
+	unsigned long nr_pages = size >> PAGE_SHIFT;
+
+	start = (unsigned long)__va(start);
+	if (remove_section_mapping(start, start + size))
+		return -EINVAL;
+
+	return __remove_pages(start_pfn, nr_pages);
+}
+#endif
 #endif /* CONFIG_MEMORY_HOTPLUG */
 
 /*
diff --git a/arch/s390/mm/init.c b/arch/s390/mm/init.c
index 6adbc08..501b20e 100644
--- a/arch/s390/mm/init.c
+++ b/arch/s390/mm/init.c
@@ -257,4 +257,16 @@ int arch_add_memory(int nid, u64 start, u64 size)
 		vmem_remove_mapping(start, size);
 	return rc;
 }
+
+#ifdef CONFIG_MEMORY_HOTREMOVE
+int arch_remove_memory(u64 start, u64 size)
+{
+	/*
+	 * There is no hardware or firmware interface which could trigger a
+	 * hot memory remove on s390. So there is nothing that needs to be
+	 * implemented.
+	 */
+	return -EBUSY;
+}
+#endif
 #endif /* CONFIG_MEMORY_HOTPLUG */
diff --git a/arch/sh/mm/init.c b/arch/sh/mm/init.c
index 82cc576..fc84491 100644
--- a/arch/sh/mm/init.c
+++ b/arch/sh/mm/init.c
@@ -558,4 +558,19 @@ int memory_add_physaddr_to_nid(u64 addr)
 EXPORT_SYMBOL_GPL(memory_add_physaddr_to_nid);
 #endif
 
+#ifdef CONFIG_MEMORY_HOTREMOVE
+int arch_remove_memory(u64 start, u64 size)
+{
+	unsigned long start_pfn = start >> PAGE_SHIFT;
+	unsigned long nr_pages = size >> PAGE_SHIFT;
+	int ret;
+
+	ret = __remove_pages(start_pfn, nr_pages);
+	if (unlikely(ret))
+		pr_warn("%s: Failed, __remove_pages() == %d\n", __func__,
+			ret);
+
+	return ret;
+}
+#endif
 #endif /* CONFIG_MEMORY_HOTPLUG */
diff --git a/arch/tile/mm/init.c b/arch/tile/mm/init.c
index ef29d6c..2749515 100644
--- a/arch/tile/mm/init.c
+++ b/arch/tile/mm/init.c
@@ -935,6 +935,14 @@ int remove_memory(u64 start, u64 size)
 {
 	return -EINVAL;
 }
+
+#ifdef CONFIG_MEMORY_HOTREMOVE
+int arch_remove_memory(u64 start, u64 size)
+{
+	/* TODO */
+	return -EBUSY;
+}
+#endif
 #endif
 
 struct kmem_cache *pgd_cache;
diff --git a/arch/x86/include/asm/pgtable_types.h b/arch/x86/include/asm/pgtable_types.h
index 013286a..b725af2 100644
--- a/arch/x86/include/asm/pgtable_types.h
+++ b/arch/x86/include/asm/pgtable_types.h
@@ -334,6 +334,7 @@ static inline void update_page_count(int level, unsigned long pages) { }
  * as a pte too.
  */
 extern pte_t *lookup_address(unsigned long address, unsigned int *level);
+extern int __split_large_page(pte_t *kpte, unsigned long address, pte_t *pbase);
 
 #endif	/* !__ASSEMBLY__ */
 
diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c
index 575d86f..41eefe8 100644
--- a/arch/x86/mm/init_32.c
+++ b/arch/x86/mm/init_32.c
@@ -842,6 +842,16 @@ int arch_add_memory(int nid, u64 start, u64 size)
 
 	return __add_pages(nid, zone, start_pfn, nr_pages);
 }
+
+#ifdef CONFIG_MEMORY_HOTREMOVE
+int arch_remove_memory(u64 start, u64 size)
+{
+	unsigned long start_pfn = start >> PAGE_SHIFT;
+	unsigned long nr_pages = size >> PAGE_SHIFT;
+
+	return __remove_pages(start_pfn, nr_pages);
+}
+#endif
 #endif
 
 /*
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 2b6b4a3..e0d88ba 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -675,6 +675,166 @@ int arch_add_memory(int nid, u64 start, u64 size)
 }
 EXPORT_SYMBOL_GPL(arch_add_memory);
 
+static void __meminit
+phys_pte_remove(pte_t *pte_page, unsigned long addr, unsigned long end)
+{
+	unsigned pages = 0;
+	int i = pte_index(addr);
+
+	pte_t *pte = pte_page + pte_index(addr);
+
+	for (; i < PTRS_PER_PTE; i++, addr += PAGE_SIZE, pte++) {
+
+		if (addr >= end)
+			break;
+
+		if (!pte_present(*pte))
+			continue;
+
+		pages++;
+		set_pte(pte, __pte(0));
+	}
+
+	update_page_count(PG_LEVEL_4K, -pages);
+}
+
+static void __meminit
+phys_pmd_remove(pmd_t *pmd_page, unsigned long addr, unsigned long end)
+{
+	unsigned long pages = 0, next;
+	int i = pmd_index(addr);
+
+	for (; i < PTRS_PER_PMD; i++, addr = next) {
+		unsigned long pte_phys;
+		pmd_t *pmd = pmd_page + pmd_index(addr);
+		pte_t *pte;
+
+		if (addr >= end)
+			break;
+
+		next = (addr & PMD_MASK) + PMD_SIZE;
+
+		if (!pmd_present(*pmd))
+			continue;
+
+		if (pmd_large(*pmd)) {
+			if ((addr & ~PMD_MASK) == 0 && next <= end) {
+				set_pmd(pmd, __pmd(0));
+				pages++;
+				continue;
+			}
+
+			/*
+			 * We use 2M page, but we need to remove part of them,
+			 * so split 2M page to 4K page.
+			 */
+			pte = alloc_low_page(&pte_phys);
+			__split_large_page((pte_t *)pmd, addr, pte);
+
+			spin_lock(&init_mm.page_table_lock);
+			pmd_populate_kernel(&init_mm, pmd, __va(pte_phys));
+			spin_unlock(&init_mm.page_table_lock);
+		}
+
+		spin_lock(&init_mm.page_table_lock);
+		pte = map_low_page((pte_t *)pmd_page_vaddr(*pmd));
+		phys_pte_remove(pte, addr, end);
+		unmap_low_page(pte);
+		spin_unlock(&init_mm.page_table_lock);
+	}
+	update_page_count(PG_LEVEL_2M, -pages);
+}
+
+static void __meminit
+phys_pud_remove(pud_t *pud_page, unsigned long addr, unsigned long end)
+{
+	unsigned long pages = 0, next;
+	int i = pud_index(addr);
+
+	for (; i < PTRS_PER_PUD; i++, addr = next) {
+		unsigned long pmd_phys;
+		pud_t *pud = pud_page + pud_index(addr);
+		pmd_t *pmd;
+
+		if (addr >= end)
+			break;
+
+		next = (addr & PUD_MASK) + PUD_SIZE;
+
+		if (!pud_present(*pud))
+			continue;
+
+		if (pud_large(*pud)) {
+			if ((addr & ~PUD_MASK) == 0 && next <= end) {
+				set_pud(pud, __pud(0));
+				pages++;
+				continue;
+			}
+
+			/*
+			 * We use 1G page, but we need to remove part of them,
+			 * so split 1G page to 2M page.
+			 */
+			pmd = alloc_low_page(&pmd_phys);
+			__split_large_page((pte_t *)pud, addr, (pte_t *)pmd);
+
+			spin_lock(&init_mm.page_table_lock);
+			pud_populate(&init_mm, pud, __va(pmd_phys));
+			spin_unlock(&init_mm.page_table_lock);
+		}
+
+		pmd = map_low_page(pmd_offset(pud, 0));
+		phys_pmd_remove(pmd, addr, end);
+		unmap_low_page(pmd);
+		__flush_tlb_all();
+	}
+	__flush_tlb_all();
+
+	update_page_count(PG_LEVEL_1G, -pages);
+}
+
+void __meminit
+kernel_physical_mapping_remove(unsigned long start, unsigned long end)
+{
+	unsigned long next;
+
+	start = (unsigned long)__va(start);
+	end = (unsigned long)__va(end);
+
+	for (; start < end; start = next) {
+		pgd_t *pgd = pgd_offset_k(start);
+		pud_t *pud;
+
+		next = (start + PGDIR_SIZE) & PGDIR_MASK;
+		if (next > end)
+			next = end;
+
+		if (!pgd_present(*pgd))
+			continue;
+
+		pud = map_low_page((pud_t *)pgd_page_vaddr(*pgd));
+		phys_pud_remove(pud, __pa(start), __pa(end));
+		unmap_low_page(pud);
+	}
+
+	__flush_tlb_all();
+}
+
+#ifdef CONFIG_MEMORY_HOTREMOVE
+int __ref arch_remove_memory(u64 start, u64 size)
+{
+	unsigned long start_pfn = start >> PAGE_SHIFT;
+	unsigned long nr_pages = size >> PAGE_SHIFT;
+	int ret;
+
+	ret = __remove_pages(start_pfn, nr_pages);
+	WARN_ON_ONCE(ret);
+
+	kernel_physical_mapping_remove(start, start + size);
+
+	return ret;
+}
+#endif
 #endif /* CONFIG_MEMORY_HOTPLUG */
 
 static struct kcore_list kcore_vsyscall;
diff --git a/arch/x86/mm/pageattr.c b/arch/x86/mm/pageattr.c
index a718e0d..7dcb6f9 100644
--- a/arch/x86/mm/pageattr.c
+++ b/arch/x86/mm/pageattr.c
@@ -501,21 +501,13 @@ out_unlock:
 	return do_split;
 }
 
-static int split_large_page(pte_t *kpte, unsigned long address)
+int __split_large_page(pte_t *kpte, unsigned long address, pte_t *pbase)
 {
 	unsigned long pfn, pfninc = 1;
 	unsigned int i, level;
-	pte_t *pbase, *tmp;
+	pte_t *tmp;
 	pgprot_t ref_prot;
-	struct page *base;
-
-	if (!debug_pagealloc)
-		spin_unlock(&cpa_lock);
-	base = alloc_pages(GFP_KERNEL | __GFP_NOTRACK, 0);
-	if (!debug_pagealloc)
-		spin_lock(&cpa_lock);
-	if (!base)
-		return -ENOMEM;
+	struct page *base = virt_to_page(pbase);
 
 	spin_lock(&pgd_lock);
 	/*
@@ -523,10 +515,11 @@ static int split_large_page(pte_t *kpte, unsigned long address)
 	 * up for us already:
 	 */
 	tmp = lookup_address(address, &level);
-	if (tmp != kpte)
-		goto out_unlock;
+	if (tmp != kpte) {
+		spin_unlock(&pgd_lock);
+		return 1;
+	}
 
-	pbase = (pte_t *)page_address(base);
 	paravirt_alloc_pte(&init_mm, page_to_pfn(base));
 	ref_prot = pte_pgprot(pte_clrhuge(*kpte));
 	/*
@@ -579,17 +572,27 @@ static int split_large_page(pte_t *kpte, unsigned long address)
 	 * going on.
 	 */
 	__flush_tlb_all();
+	spin_unlock(&pgd_lock);
 
-	base = NULL;
+	return 0;
+}
 
-out_unlock:
-	/*
-	 * If we dropped out via the lookup_address check under
-	 * pgd_lock then stick the page back into the pool:
-	 */
-	if (base)
+static int split_large_page(pte_t *kpte, unsigned long address)
+{
+	pte_t *pbase;
+	struct page *base;
+
+	if (!debug_pagealloc)
+		spin_unlock(&cpa_lock);
+	base = alloc_pages(GFP_KERNEL | __GFP_NOTRACK, 0);
+	if (!debug_pagealloc)
+		spin_lock(&cpa_lock);
+	if (!base)
+		return -ENOMEM;
+
+	pbase = (pte_t *)page_address(base);
+	if (__split_large_page(kpte, address, pbase))
 		__free_page(base);
-	spin_unlock(&pgd_lock);
 
 	return 0;
 }
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index 8bf820d..cdbbd79 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -85,6 +85,7 @@ extern void __online_page_free(struct page *page);
 
 #ifdef CONFIG_MEMORY_HOTREMOVE
 extern bool is_pageblock_removable_nolock(struct page *page);
+extern int arch_remove_memory(u64 start, u64 size);
 #endif /* CONFIG_MEMORY_HOTREMOVE */
 
 /* reasonably generic interface to expand the physical pages in a zone  */
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 7fbfc9f..d736df3 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -1074,6 +1074,7 @@ int __ref remove_memory(int nid, u64 start, u64 size)
 	/* remove memmap entry */
 	firmware_map_remove(start, start + size, "System RAM");
 
+	arch_remove_memory(start, size);
 out:
 	unlock_memory_hotplug();
 	return ret;
-- 
1.7.1

[RFC v9 PATCH 16/21] memory-hotplug: free memmap of sparse-vmemmap

From: <hidden>
Date: 2012-09-05 09:46:46

From: Yasuaki Ishimatsu <redacted>

All pages of virtual mapping in removed memory cannot be freed, since some pages
used as PGD/PUD includes not only removed memory but also other memory. So the
patch checks whether page can be freed or not.

How to check whether page can be freed or not?
 1. When removing memory, the page structs of the revmoved memory are filled
    with 0FD.
 2. All page structs are filled with 0xFD on PT/PMD, PT/PMD can be cleared.
    In this case, the page used as PT/PMD can be freed.

Applying patch, __remove_section() of CONFIG_SPARSEMEM_VMEMMAP is integrated
into one. So __remove_section() of CONFIG_SPARSEMEM_VMEMMAP is deleted.

Note:  vmemmap_kfree() and vmemmap_free_bootmem() are not implemented for ia64,
ppc, s390, and sparc.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
 arch/ia64/mm/discontig.c  |    8 +++
 arch/powerpc/mm/init_64.c |    8 +++
 arch/s390/mm/vmem.c       |    8 +++
 arch/sparc/mm/init_64.c   |    8 +++
 arch/x86/mm/init_64.c     |  119 +++++++++++++++++++++++++++++++++++++++++++++
 include/linux/mm.h        |    2 +
 mm/memory_hotplug.c       |   17 +------
 mm/sparse.c               |    5 +-
 8 files changed, 158 insertions(+), 17 deletions(-)
diff --git a/arch/ia64/mm/discontig.c b/arch/ia64/mm/discontig.c
index 33943db..0d23b69 100644
--- a/arch/ia64/mm/discontig.c
+++ b/arch/ia64/mm/discontig.c
@@ -823,6 +823,14 @@ int __meminit vmemmap_populate(struct page *start_page,
 	return vmemmap_populate_basepages(start_page, size, node);
 }
 
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
 void register_page_bootmem_memmap(unsigned long section_nr,
 				  struct page *start_page, unsigned long size)
 {
diff --git a/arch/powerpc/mm/init_64.c b/arch/powerpc/mm/init_64.c
index 3690c44..835a2b3 100644
--- a/arch/powerpc/mm/init_64.c
+++ b/arch/powerpc/mm/init_64.c
@@ -299,6 +299,14 @@ int __meminit vmemmap_populate(struct page *start_page,
 	return 0;
 }
 
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
 void register_page_bootmem_memmap(unsigned long section_nr,
 				  struct page *start_page, unsigned long size)
 {
diff --git a/arch/s390/mm/vmem.c b/arch/s390/mm/vmem.c
index eda55cd..4b42b0b 100644
--- a/arch/s390/mm/vmem.c
+++ b/arch/s390/mm/vmem.c
@@ -227,6 +227,14 @@ out:
 	return ret;
 }
 
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
 void register_page_bootmem_memmap(unsigned long section_nr,
 				  struct page *start_page, unsigned long size)
 {
diff --git a/arch/sparc/mm/init_64.c b/arch/sparc/mm/init_64.c
index add1cc7..1384826 100644
--- a/arch/sparc/mm/init_64.c
+++ b/arch/sparc/mm/init_64.c
@@ -2078,6 +2078,14 @@ void __meminit vmemmap_populate_print_last(void)
 	}
 }
 
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
 void register_page_bootmem_memmap(unsigned long section_nr,
 				  struct page *start_page, unsigned long size)
 {
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 0075592..4e8f8a4 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -1138,6 +1138,125 @@ vmemmap_populate(struct page *start_page, unsigned long size, int node)
 	return 0;
 }
 
+#define PAGE_INUSE 0xFD
+
+unsigned long find_and_clear_pte_page(unsigned long addr, unsigned long end,
+			    struct page **pp, int *page_size)
+{
+	pgd_t *pgd;
+	pud_t *pud;
+	pmd_t *pmd;
+	pte_t *pte;
+	void *page_addr;
+	unsigned long next;
+
+	*pp = NULL;
+
+	pgd = pgd_offset_k(addr);
+	if (pgd_none(*pgd))
+		return pgd_addr_end(addr, end);
+
+	pud = pud_offset(pgd, addr);
+	if (pud_none(*pud))
+		return pud_addr_end(addr, end);
+
+	if (!cpu_has_pse) {
+		next = (addr + PAGE_SIZE) & PAGE_MASK;
+		pmd = pmd_offset(pud, addr);
+		if (pmd_none(*pmd))
+			return next;
+
+		pte = pte_offset_kernel(pmd, addr);
+		if (pte_none(*pte))
+			return next;
+
+		*page_size = PAGE_SIZE;
+		*pp = pte_page(*pte);
+	} else {
+		next = pmd_addr_end(addr, end);
+
+		pmd = pmd_offset(pud, addr);
+		if (pmd_none(*pmd))
+			return next;
+
+		*page_size = PMD_SIZE;
+		*pp = pmd_page(*pmd);
+	}
+
+	/*
+	 * Removed page structs are filled with 0xFD.
+	 */
+	memset((void *)addr, PAGE_INUSE, next - addr);
+
+	page_addr = page_address(*pp);
+
+	/*
+	 * Check the page is filled with 0xFD or not.
+	 * memchr_inv() returns the address. In this case, we cannot
+	 * clear PTE/PUD entry, since the page is used by other.
+	 * So we cannot also free the page.
+	 *
+	 * memchr_inv() returns NULL. In this case, we can clear
+	 * PTE/PUD entry, since the page is not used by other.
+	 * So we can also free the page.
+	 */
+	if (memchr_inv(page_addr, PAGE_INUSE, *page_size)) {
+		*pp = NULL;
+		return next;
+	}
+
+	if (!cpu_has_pse)
+		pte_clear(&init_mm, addr, pte);
+	else
+		pmd_clear(pmd);
+
+	return next;
+}
+
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+	unsigned long addr = (unsigned long)memmap;
+	unsigned long end = (unsigned long)(memmap + nr_pages);
+	unsigned long next;
+	struct page *page;
+	int page_size;
+
+	for (; addr < end; addr = next) {
+		page = NULL;
+		page_size = 0;
+		next = find_and_clear_pte_page(addr, end, &page, &page_size);
+		if (!page)
+			continue;
+
+		free_pages((unsigned long)page_address(page),
+			    get_order(page_size));
+		__flush_tlb_one(addr);
+	}
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+	unsigned long addr = (unsigned long)memmap;
+	unsigned long end = (unsigned long)(memmap + nr_pages);
+	unsigned long next;
+	struct page *page;
+	int page_size;
+	unsigned long magic;
+
+	for (; addr < end; addr = next) {
+		page = NULL;
+		page_size = 0;
+		next = find_and_clear_pte_page(addr, end, &page, &page_size);
+		if (!page)
+			continue;
+
+		magic = (unsigned long) page->lru.next;
+		if (magic == SECTION_INFO)
+			put_page_bootmem(page);
+		flush_tlb_kernel_range(addr, end);
+	}
+}
+
 void register_page_bootmem_memmap(unsigned long section_nr,
 				  struct page *start_page, unsigned long size)
 {
diff --git a/include/linux/mm.h b/include/linux/mm.h
index c607913..fb0d1fc 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1620,6 +1620,8 @@ int vmemmap_populate(struct page *start_page, unsigned long pages, int node);
 void vmemmap_populate_print_last(void);
 void register_page_bootmem_memmap(unsigned long section_nr, struct page *map,
 				  unsigned long size);
+void vmemmap_kfree(struct page *memmpa, unsigned long nr_pages);
+void vmemmap_free_bootmem(struct page *memmpa, unsigned long nr_pages);
 
 enum mf_flags {
 	MF_COUNT_INCREASED = 1 << 0,
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 647a7f2..c54922c 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -308,19 +308,6 @@ static int __meminit __add_section(int nid, struct zone *zone,
 	return register_new_memory(nid, __pfn_to_section(phys_start_pfn));
 }
 
-#ifdef CONFIG_SPARSEMEM_VMEMMAP
-static int __remove_section(struct zone *zone, struct mem_section *ms)
-{
-	int ret = -EINVAL;
-
-	if (!valid_section(ms))
-		return ret;
-
-	ret = unregister_memory_section(ms);
-
-	return ret;
-}
-#else
 static int __remove_section(struct zone *zone, struct mem_section *ms)
 {
 	unsigned long flags;
@@ -337,9 +324,9 @@ static int __remove_section(struct zone *zone, struct mem_section *ms)
 	pgdat_resize_lock(pgdat, &flags);
 	sparse_remove_one_section(zone, ms);
 	pgdat_resize_unlock(pgdat, &flags);
-	return 0;
+
+	return ret;
 }
-#endif
 
 /*
  * Reasonably generic function for adding memory.  It is
diff --git a/mm/sparse.c b/mm/sparse.c
index fac95f2..ab9d755 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -613,12 +613,13 @@ static inline struct page *kmalloc_section_memmap(unsigned long pnum, int nid,
 	/* This will make the necessary allocations eventually. */
 	return sparse_mem_map_populate(pnum, nid);
 }
-static void __kfree_section_memmap(struct page *memmap, unsigned long nr_pages)
+static void __kfree_section_memmap(struct page *page, unsigned long nr_pages)
 {
-	return; /* XXX: Not implemented yet */
+	vmemmap_kfree(page, nr_pages);
 }
 static void free_map_bootmem(struct page *page, unsigned long nr_pages)
 {
+	vmemmap_free_bootmem(page, nr_pages);
 }
 #else
 static struct page *__kmalloc_section_memmap(unsigned long nr_pages)
-- 
1.7.1

[RFC v9 PATCH 17/21] memory_hotplug: clear zone when the memory is removed

From: <hidden>
Date: 2012-09-05 09:47:21

From: Yasuaki Ishimatsu <redacted>

When a memory is added, we update zone's and pgdat's start_pfn and spanned_pages
in the function __add_zone(). So we should revert these when the memory is
removed. Add a new function __remove_zone() to do this.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 mm/memory_hotplug.c |  207 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 207 insertions(+), 0 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index c54922c..afda7e9 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -308,10 +308,213 @@ static int __meminit __add_section(int nid, struct zone *zone,
 	return register_new_memory(nid, __pfn_to_section(phys_start_pfn));
 }
 
+/* find the smallest valid pfn in the range [start_pfn, end_pfn) */
+static int find_smallest_section_pfn(int nid, struct zone *zone,
+				     unsigned long start_pfn,
+				     unsigned long end_pfn)
+{
+	struct mem_section *ms;
+
+	for (; start_pfn < end_pfn; start_pfn += PAGES_PER_SECTION) {
+		ms = __pfn_to_section(start_pfn);
+
+		if (unlikely(!valid_section(ms)))
+			continue;
+
+		if (unlikely(pfn_to_nid(start_pfn)) != nid)
+			continue;
+
+		if (zone && zone != page_zone(pfn_to_page(start_pfn)))
+			continue;
+
+		return start_pfn;
+	}
+
+	return 0;
+}
+
+/* find the biggest valid pfn in the range [start_pfn, end_pfn). */
+static int find_biggest_section_pfn(int nid, struct zone *zone,
+				    unsigned long start_pfn,
+				    unsigned long end_pfn)
+{
+	struct mem_section *ms;
+	unsigned long pfn;
+
+	/* pfn is the end pfn of a memory section. */
+	pfn = end_pfn - 1;
+	for (; pfn >= start_pfn; pfn -= PAGES_PER_SECTION) {
+		ms = __pfn_to_section(pfn);
+
+		if (unlikely(!valid_section(ms)))
+			continue;
+
+		if (unlikely(pfn_to_nid(pfn)) != nid)
+			continue;
+
+		if (zone && zone != page_zone(pfn_to_page(pfn)))
+			continue;
+
+		return pfn;
+	}
+
+	return 0;
+}
+
+static void shrink_zone_span(struct zone *zone, unsigned long start_pfn,
+			     unsigned long end_pfn)
+{
+	unsigned long zone_start_pfn =  zone->zone_start_pfn;
+	unsigned long zone_end_pfn = zone->zone_start_pfn + zone->spanned_pages;
+	unsigned long pfn;
+	struct mem_section *ms;
+	int nid = zone_to_nid(zone);
+
+	zone_span_writelock(zone);
+	if (zone_start_pfn == start_pfn) {
+		/*
+		 * If the section is smallest section in the zone, it need
+		 * shrink zone->zone_start_pfn and zone->zone_spanned_pages.
+		 * In this case, we find second smallest valid mem_section
+		 * for shrinking zone.
+		 */
+		pfn = find_smallest_section_pfn(nid, zone, end_pfn,
+						zone_end_pfn);
+		if (pfn) {
+			zone->zone_start_pfn = pfn;
+			zone->spanned_pages = zone_end_pfn - pfn;
+		}
+	} else if (zone_end_pfn == end_pfn) {
+		/*
+		 * If the section is biggest section in the zone, it need
+		 * shrink zone->spanned_pages.
+		 * In this case, we find second biggest valid mem_section for
+		 * shrinking zone.
+		 */
+		pfn = find_biggest_section_pfn(nid, zone, zone_start_pfn,
+					       start_pfn);
+		if (pfn)
+			zone->spanned_pages = pfn - zone_start_pfn + 1;
+	}
+
+	/*
+	 * The section is not biggest or smallest mem_section in the zone, it
+	 * only creates a hole in the zone. So in this case, we need not
+	 * change the zone. But perhaps, the zone has only hole data. Thus
+	 * it check the zone has only hole or not.
+	 */
+	pfn = zone_start_pfn;
+	for (; pfn < zone_end_pfn; pfn += PAGES_PER_SECTION) {
+		ms = __pfn_to_section(pfn);
+
+		if (unlikely(!valid_section(ms)))
+			continue;
+
+		if (page_zone(pfn_to_page(pfn)) != zone)
+			continue;
+
+		 /* If the section is current section, it continues the loop */
+		if (start_pfn == pfn)
+			continue;
+
+		/* If we find valid section, we have nothing to do */
+		zone_span_writeunlock(zone);
+		return;
+	}
+
+	/* The zone has no valid section */
+	zone->zone_start_pfn = 0;
+	zone->spanned_pages = 0;
+	zone_span_writeunlock(zone);
+}
+
+static void shrink_pgdat_span(struct pglist_data *pgdat,
+			      unsigned long start_pfn, unsigned long end_pfn)
+{
+	unsigned long pgdat_start_pfn =  pgdat->node_start_pfn;
+	unsigned long pgdat_end_pfn =
+		pgdat->node_start_pfn + pgdat->node_spanned_pages;
+	unsigned long pfn;
+	struct mem_section *ms;
+	int nid = pgdat->node_id;
+
+	if (pgdat_start_pfn == start_pfn) {
+		/*
+		 * If the section is smallest section in the pgdat, it need
+		 * shrink pgdat->node_start_pfn and pgdat->node_spanned_pages.
+		 * In this case, we find second smallest valid mem_section
+		 * for shrinking zone.
+		 */
+		pfn = find_smallest_section_pfn(nid, NULL, end_pfn,
+						pgdat_end_pfn);
+		if (pfn) {
+			pgdat->node_start_pfn = pfn;
+			pgdat->node_spanned_pages = pgdat_end_pfn - pfn;
+		}
+	} else if (pgdat_end_pfn == end_pfn) {
+		/*
+		 * If the section is biggest section in the pgdat, it need
+		 * shrink pgdat->node_spanned_pages.
+		 * In this case, we find second biggest valid mem_section for
+		 * shrinking zone.
+		 */
+		pfn = find_biggest_section_pfn(nid, NULL, pgdat_start_pfn,
+					       start_pfn);
+		if (pfn)
+			pgdat->node_spanned_pages = pfn - pgdat_start_pfn + 1;
+	}
+
+	/*
+	 * If the section is not biggest or smallest mem_section in the pgdat,
+	 * it only creates a hole in the pgdat. So in this case, we need not
+	 * change the pgdat.
+	 * But perhaps, the pgdat has only hole data. Thus it check the pgdat
+	 * has only hole or not.
+	 */
+	pfn = pgdat_start_pfn;
+	for (; pfn < pgdat_end_pfn; pfn += PAGES_PER_SECTION) {
+		ms = __pfn_to_section(pfn);
+
+		if (unlikely(!valid_section(ms)))
+			continue;
+
+		if (pfn_to_nid(pfn) != nid)
+			continue;
+
+		 /* If the section is current section, it continues the loop */
+		if (start_pfn == pfn)
+			continue;
+
+		/* If we find valid section, we have nothing to do */
+		return;
+	}
+
+	/* The pgdat has no valid section */
+	pgdat->node_start_pfn = 0;
+	pgdat->node_spanned_pages = 0;
+}
+
+static void __remove_zone(struct zone *zone, unsigned long start_pfn)
+{
+	struct pglist_data *pgdat = zone->zone_pgdat;
+	int nr_pages = PAGES_PER_SECTION;
+	int zone_type;
+	unsigned long flags;
+
+	zone_type = zone - pgdat->node_zones;
+
+	pgdat_resize_lock(zone->zone_pgdat, &flags);
+	shrink_zone_span(zone, start_pfn, start_pfn + nr_pages);
+	shrink_pgdat_span(pgdat, start_pfn, start_pfn + nr_pages);
+	pgdat_resize_unlock(zone->zone_pgdat, &flags);
+}
+
 static int __remove_section(struct zone *zone, struct mem_section *ms)
 {
 	unsigned long flags;
 	struct pglist_data *pgdat = zone->zone_pgdat;
+	unsigned long start_pfn;
+	int scn_nr;
 	int ret = -EINVAL;
 
 	if (!valid_section(ms))
@@ -321,6 +524,10 @@ static int __remove_section(struct zone *zone, struct mem_section *ms)
 	if (ret)
 		return ret;
 
+	scn_nr = __section_nr(ms);
+	start_pfn = section_nr_to_pfn(scn_nr);
+	__remove_zone(zone, start_pfn);
+
 	pgdat_resize_lock(pgdat, &flags);
 	sparse_remove_one_section(zone, ms);
 	pgdat_resize_unlock(pgdat, &flags);
-- 
1.7.1

[RFC v9 PATCH 18/21] memory-hotplug: add node_device_release

From: <hidden>
Date: 2012-09-05 10:00:10

From: Yasuaki Ishimatsu <redacted>

When calling unregister_node(), the function shows following message at
device_release().

Device 'node2' does not have a release() function, it is broken and must be
fixed.

So the patch implements node_device_release()

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 drivers/base/node.c |   11 +++++++++++
 1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/drivers/base/node.c b/drivers/base/node.c
index af1a177..07523fb 100644
--- a/drivers/base/node.c
+++ b/drivers/base/node.c
@@ -252,6 +252,16 @@ static inline void hugetlb_register_node(struct node *node) {}
 static inline void hugetlb_unregister_node(struct node *node) {}
 #endif
 
+static void node_device_release(struct device *dev)
+{
+	struct node *node_dev = to_node(dev);
+
+#if defined(CONFIG_MEMORY_HOTPLUG_SPARSE) && defined(CONFIG_HUGETLBFS)
+	flush_work(&node_dev->node_work);
+#endif
+
+	memset(node_dev, 0, sizeof(struct node));
+}
 
 /*
  * register_node - Setup a sysfs device for a node.
@@ -265,6 +275,7 @@ int register_node(struct node *node, int num, struct node *parent)
 
 	node->dev.id = num;
 	node->dev.bus = &node_subsys;
+	node->dev.release = node_device_release;
 	error = device_register(&node->dev);
 
 	if (!error){
-- 
1.7.1

Re: [RFC v9 PATCH 20/21] memory-hotplug: clear hwpoisoned flag when onlining pages

From: andywu106建国 <hidden>
Date: 2012-09-06 07:28:01

2012/9/5 [off-list ref]
quoted hunk
From: Wen Congyang <redacted>

hwpoisoned may set when we offline a page by the sysfs interface
/sys/devices/system/memory/soft_offline_page or
/sys/devices/system/memory/hard_offline_page. If we don't clear
this flag when onlining pages, this page can't be freed, and will
not in free list. So we can't offline these pages again. So we
should clear this flag when onlining pages.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 mm/memory_hotplug.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 270c249..140c080 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -661,6 +661,11 @@ EXPORT_SYMBOL_GPL(__online_page_increment_counters);

 void __online_page_free(struct page *page)
 {
+#ifdef CONFIG_MEMORY_FAILURE
+       /* The page may be marked HWPoisoned by soft/hard offline page */
+       ClearPageHWPoison(page);
Hi Congyang,
I think you should decrease mce_bad_pages counter her
atomic_long_sub(1, &mce_bad_pages);
+#endif
+
        ClearPageReserved(page);
        init_page_count(page);
        __free_page(page);
--
1.7.1

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: [RFC v9 PATCH 20/21] memory-hotplug: clear hwpoisoned flag when onlining pages

From: Wen Congyang <hidden>
Date: 2012-09-06 08:36:29

At 09/06/2012 03:27 PM, andywu106=E5=BB=BA=E5=9B=BD Wrote:
2012/9/5 [off-list ref]
quoted
From: Wen Congyang <redacted>

hwpoisoned may set when we offline a page by the sysfs interface
/sys/devices/system/memory/soft=5Foffline=5Fpage or
/sys/devices/system/memory/hard=5Foffline=5Fpage. If we don't clear
this flag when onlining pages, this page can't be freed, and will
not in free list. So we can't offline these pages again. So we
should clear this flag when onlining pages.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
 mm/memory=5Fhotplug.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/mm/memory=5Fhotplug.c b/mm/memory=5Fhotplug.c
index 270c249..140c080 100644
--- a/mm/memory=5Fhotplug.c
+++ b/mm/memory=5Fhotplug.c
@@ -661,6 +661,11 @@ EXPORT=5FSYMBOL=5FGPL(=5F=5Fonline=5Fpage=5Fincreme=
nt=5Fcounters);
quoted
 void =5F=5Fonline=5Fpage=5Ffree(struct page *page)
 {
+#ifdef CONFIG=5FMEMORY=5FFAILURE
+       /* The page may be marked HWPoisoned by soft/hard offline page */
+       ClearPageHWPoison(page);
=20
Hi Congyang,
I think you should decrease mce=5Fbad=5Fpages counter her
atomic=5Flong=5Fsub(1, &mce=5Fbad=5Fpages);
Yes, thanks for pointing it out.

Thanks
Wen Congyang
=20
quoted
+#endif
+
        ClearPageReserved(page);
        init=5Fpage=5Fcount(page);
        =5F=5Ffree=5Fpage(page);
--
1.7.1

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=3Dmailto:"dont@kvack.org"> email@kvack.org </a>
=20
=

Re: [RFC v9 PATCH 05/21] memory-hotplug: check whether memory is present or not

From: Yasuaki Ishimatsu <hidden>
Date: 2012-09-11 02:25:53

Hi Wen,

2012/09/11 11:15, Wen Congyang wrote:
Hi, ishimatsu

At 09/05/2012 05:25 PM, wency@cn.fujitsu.com Wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

If system supports memory hot-remove, online_pages() may online removed pages.
So online_pages() need to check whether onlining pages are present or not.
Because we use memory_block_change_state() to hotremoving memory, I think
this patch can be removed. What do you think?
Pleae teach me detals a little more. If we use memory_block_change_state(),
does the conflict never occur? Why?

Thansk,
Yasuaki Ishimatsu
Thanks
Wen Congyang
quoted
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  include/linux/mmzone.h |   19 +++++++++++++++++++
  mm/memory_hotplug.c    |   13 +++++++++++++
  2 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 2daa54f..ac3ae30 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -1180,6 +1180,25 @@ void sparse_init(void);
  #define sparse_index_init(_sec, _nid)  do {} while (0)
  #endif /* CONFIG_SPARSEMEM */

+#ifdef CONFIG_SPARSEMEM
+static inline int pfns_present(unsigned long pfn, unsigned long nr_pages)
+{
+	int i;
+	for (i = 0; i < nr_pages; i++) {
+		if (pfn_present(pfn + i))
+			continue;
+		else
+			return -EINVAL;
+	}
+	return 0;
+}
+#else
+static inline int pfns_present(unsigned long pfn, unsigned long nr_pages)
+{
+	return 0;
+}
+#endif /* CONFIG_SPARSEMEM*/
+
  #ifdef CONFIG_NODES_SPAN_OTHER_NODES
  bool early_pfn_in_nid(unsigned long pfn, int nid);
  #else
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 49f7747..299747d 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -467,6 +467,19 @@ int __ref online_pages(unsigned long pfn, unsigned long nr_pages)
  	struct memory_notify arg;

  	lock_memory_hotplug();
+	/*
+	 * If system supports memory hot-remove, the memory may have been
+	 * removed. So we check whether the memory has been removed or not.
+	 *
+	 * Note: When CONFIG_SPARSEMEM is defined, pfns_present() become
+	 *       effective. If CONFIG_SPARSEMEM is not defined, pfns_present()
+	 *       always returns 0.
+	 */
+	ret = pfns_present(pfn, nr_pages);
+	if (ret) {
+		unlock_memory_hotplug();
+		return ret;
+	}
  	arg.start_pfn = pfn;
  	arg.nr_pages = nr_pages;
  	arg.status_change_nid = -1;

Re: [RFC v9 PATCH 05/21] memory-hotplug: check whether memory is present or not

From: Wen Congyang <hidden>
Date: 2012-09-11 02:40:45

At 09/11/2012 10:24 AM, Yasuaki Ishimatsu Wrote:
Hi Wen,

2012/09/11 11:15, Wen Congyang wrote:
quoted
Hi, ishimatsu

At 09/05/2012 05:25 PM, wency@cn.fujitsu.com Wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

If system supports memory hot-remove, online_pages() may online
removed pages.
So online_pages() need to check whether onlining pages are present or
not.
Because we use memory_block_change_state() to hotremoving memory, I think
this patch can be removed. What do you think?
Pleae teach me detals a little more. If we use memory_block_change_state(),
does the conflict never occur? Why?
I misunderstand sth, please ignore it.

Wen Congyang
Thansk,
Yasuaki Ishimatsu
quoted
Thanks
Wen Congyang
quoted
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  include/linux/mmzone.h |   19 +++++++++++++++++++
  mm/memory_hotplug.c    |   13 +++++++++++++
  2 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 2daa54f..ac3ae30 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -1180,6 +1180,25 @@ void sparse_init(void);
  #define sparse_index_init(_sec, _nid)  do {} while (0)
  #endif /* CONFIG_SPARSEMEM */

+#ifdef CONFIG_SPARSEMEM
+static inline int pfns_present(unsigned long pfn, unsigned long
nr_pages)
+{
+    int i;
+    for (i = 0; i < nr_pages; i++) {
+        if (pfn_present(pfn + i))
+            continue;
+        else
+            return -EINVAL;
+    }
+    return 0;
+}
+#else
+static inline int pfns_present(unsigned long pfn, unsigned long
nr_pages)
+{
+    return 0;
+}
+#endif /* CONFIG_SPARSEMEM*/
+
  #ifdef CONFIG_NODES_SPAN_OTHER_NODES
  bool early_pfn_in_nid(unsigned long pfn, int nid);
  #else
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 49f7747..299747d 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -467,6 +467,19 @@ int __ref online_pages(unsigned long pfn,
unsigned long nr_pages)
      struct memory_notify arg;

      lock_memory_hotplug();
+    /*
+     * If system supports memory hot-remove, the memory may have been
+     * removed. So we check whether the memory has been removed or not.
+     *
+     * Note: When CONFIG_SPARSEMEM is defined, pfns_present() become
+     *       effective. If CONFIG_SPARSEMEM is not defined,
pfns_present()
+     *       always returns 0.
+     */
+    ret = pfns_present(pfn, nr_pages);
+    if (ret) {
+        unlock_memory_hotplug();
+        return ret;
+    }
      arg.start_pfn = pfn;
      arg.nr_pages = nr_pages;
      arg.status_change_nid = -1;

Re: [RFC v9 PATCH 05/21] memory-hotplug: check whether memory is present or not

From: Wen Congyang <hidden>
Date: 2012-09-11 02:45:37

Hi, ishimatsu

At 09/05/2012 05:25 PM, wency@cn.fujitsu.com Wrote:
From: Yasuaki Ishimatsu <redacted>

If system supports memory hot-remove, online_pages() may online removed pages.
So online_pages() need to check whether onlining pages are present or not.
Because we use memory_block_change_state() to hotremoving memory, I think
this patch can be removed. What do you think?

Thanks
Wen Congyang
quoted hunk
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
 include/linux/mmzone.h |   19 +++++++++++++++++++
 mm/memory_hotplug.c    |   13 +++++++++++++
 2 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 2daa54f..ac3ae30 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -1180,6 +1180,25 @@ void sparse_init(void);
 #define sparse_index_init(_sec, _nid)  do {} while (0)
 #endif /* CONFIG_SPARSEMEM */
 
+#ifdef CONFIG_SPARSEMEM
+static inline int pfns_present(unsigned long pfn, unsigned long nr_pages)
+{
+	int i;
+	for (i = 0; i < nr_pages; i++) {
+		if (pfn_present(pfn + i))
+			continue;
+		else
+			return -EINVAL;
+	}
+	return 0;
+}
+#else
+static inline int pfns_present(unsigned long pfn, unsigned long nr_pages)
+{
+	return 0;
+}
+#endif /* CONFIG_SPARSEMEM*/
+
 #ifdef CONFIG_NODES_SPAN_OTHER_NODES
 bool early_pfn_in_nid(unsigned long pfn, int nid);
 #else
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 49f7747..299747d 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -467,6 +467,19 @@ int __ref online_pages(unsigned long pfn, unsigned long nr_pages)
 	struct memory_notify arg;
 
 	lock_memory_hotplug();
+	/*
+	 * If system supports memory hot-remove, the memory may have been
+	 * removed. So we check whether the memory has been removed or not.
+	 *
+	 * Note: When CONFIG_SPARSEMEM is defined, pfns_present() become
+	 *       effective. If CONFIG_SPARSEMEM is not defined, pfns_present()
+	 *       always returns 0.
+	 */
+	ret = pfns_present(pfn, nr_pages);
+	if (ret) {
+		unlock_memory_hotplug();
+		return ret;
+	}
 	arg.start_pfn = pfn;
 	arg.nr_pages = nr_pages;
 	arg.status_change_nid = -1;

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Vasilis Liaskovitis <hidden>
Date: 2012-09-26 16:47:00

Hi,

I am testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

After succesfull hot-add and online, I am doing a hot-remove with "echo 1 > /sys/bus/acpi/devices/PNP/eject"
When I do the OSPM-eject, I often get slab corruption in "acpi-state" cache, or in other caches

[  170.566995] Slab corruption (Not tainted): Acpi-State start=ffff88009fc1e548, len=80
[  170.567265] Redzone: 0x0/0x0.
[  170.567399] Last user: [<          (null)>](0x0)
[  170.567667] 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568078] 010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568487] 020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568894] 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569302] 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569712] Prev obj: start=000000009fc1e4d0, len=80
[  170.569869] BUG: unable to handle kernel paging request at 000000009fc1e520
[  170.570171] IP: [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.570397] PGD 7cf37067 PUD 0 
[  170.570619] Oops: 0000 [#1] SMP 
[  170.570843] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis microcode tpm tpm_bios psmouse parport_pc serio_raw evdev parport i2c_piix4 processor thermal_sys i2c_core button ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net virtio_blk ata_piix libata scsi_mod virtio_pci virtio_ring virtio
[  170.573474] CPU 0 
[  170.573568] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[  170.573830] RIP: 0010:[<ffffffff8112803c>]  [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.574106] RSP: 0018:ffff88003eaf3a70  EFLAGS: 00010202
[  170.574268] RAX: 000000009fc1e4c8 RBX: 0000000000000002 RCX: 00000000000024b8
[  170.574468] RDX: 000000009fc1e4c8 RSI: 000000009fc1e4c8 RDI: ffff88003e9bb980
[  170.574668] RBP: ffff88003e9bb980 R08: ffff880037964078 R09: 0000000000000000
[  170.574870] R10: 000000000000021e R11: 0000000000000002 R12: 000000009fc1e4c8
[  170.575070] R13: 000000009fc1e520 R14: 000000000000004f R15: 00000000ffffffa5
[  170.575274] FS:  00007fc6b7530700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[  170.575494] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  170.575665] CR2: 000000009fc1e520 CR3: 000000007c9c1000 CR4: 00000000000006f0
[  170.575870] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  170.576075] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  170.576276] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[  170.576507] Stack:
[  170.576599]  0000000000000010 0000000001893fbe ffff88009fc1e000 0000000000000050
[  170.576938]  000000009fc1e4c8 000000000000004f 00000000ffffffa5 ffffffff8112899f
[  170.576938]  ffff88003eb309d8 ffffffff81712d6d ffff88003e9bb980 ffff88009fc1e540
[  170.576938] Call Trace:
[  170.576938]  [<ffffffff8112899f>] ? check_poison_obj+0x1df/0x1f0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff81128a9d>] ? cache_alloc_debugcheck_after.isra.52+0xed/0x220
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff8112beb5>] ? kmem_cache_alloc+0xb5/0x1e0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff812edf2d>] ? acpi_ds_result_push+0x5d/0x12e
[  170.576938]  [<ffffffff812ed127>] ? acpi_ds_exec_end_op+0x28e/0x3d3
[  170.576938]  [<ffffffff812fd86a>] ? acpi_ps_parse_loop+0x79f/0x931
[  170.576938]  [<ffffffff812fdd6c>] ? acpi_ps_parse_aml+0x89/0x261
[  170.576938]  [<ffffffff812fe50c>] ? acpi_ps_execute_method+0x1be/0x266
[  170.576938]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[  170.576938]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[  170.576938]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[  170.576938]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[  170.576938]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[  170.576938]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[  170.576938]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[  170.576938]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[  170.576938]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[  170.576938]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[  170.576938]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[  170.576938]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[  170.576938] Code: cb 75 dc 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 8b 7f 0c 4c 89 e2 e8 02 fd ff ff 4c 89 e6 49 89 c5 48 89 ef e8 d4 fc ff ff <49> 8b 55 00 48 8b 30 48 c7 c7 8c 39 6f 81 31 c0 e8 3e 34 3b 00 

Other times, the problem happens on a slab object free:

[   52.313366] Offlined Pages 32768
[   52.800232] slab error in verify_redzone_free(): cache `Acpi-ParseExt': memory outside object was overwritten
[   52.801298] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12
[   52.802039] Call Trace:
[   52.802443]  [<ffffffff811280cb>] ? __slab_error.isra.46+0x1b/0x30
[   52.803199]  [<ffffffff811287b6>] ? cache_free_debugcheck+0x256/0x260
[   52.803940]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.804645]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.805321]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.806023]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.806762]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.807499]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.808183]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.808897]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.809659]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] ffff88008f809670: redzone 1:0x0, redzone 2:0x0.
[   52.810032] ------------[ cut here ]------------
[   52.810032] kernel BUG at mm/slab.c:3125!
[   52.810032] invalid opcode: 0000 [#1] SMP 
[   52.810032] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis tpm tpm_bios microcode parport_pc parport evdev processor thermal_sys psmouse i2c_piix4 serio_raw i2c_core button ext3 jbd mbcache sg sr_mod cdrom virtio_net ata_generic virtio_blk virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[   52.810032] CPU 0 
[   52.810032] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[   52.810032] RIP: 0010:[<ffffffff81128733>]  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032] RSP: 0018:ffff88003eaf3bc0  EFLAGS: 00010093
[   52.810032] RAX: 00000000017eac3c RBX: ffff88003e9bb700 RCX: 0000000002aaaaab
[   52.810032] RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000060
[   52.810032] RBP: ffff88008f809670 R08: 09f911029d74e35b R09: 0000000000000000
[   52.810032] R10: 00000000000001d3 R11: 0000000000000002 R12: ffff88008f809000
[   52.810032] R13: ffffffff812e1b0e R14: 0000000000000000 R15: 0000000000010c00
[   52.810032] FS:  00007f63fc263700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[   52.810032] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   52.810032] CR2: 00007fff8d895b78 CR3: 000000007c866000 CR4: 00000000000006f0
[   52.810032] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   52.810032] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   52.810032] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[   52.810032] Stack:
[   52.810032]  ffff88003e9bb980 ffff88008f809670 ffff880037ba8e18 ffff88008f809678
[   52.810032]  ffff88003e9bb700 0000000000000282 ffff88003e9bf270 ffffffff812e1b0e
[   52.810032]  0000000000000001 ffffffff81128fe3 ffff88003e80f5e8 ffff88003eb31748
[   52.810032] Call Trace:
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.810032]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.810032]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.810032]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.810032]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.810032]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] Code: 89 ea 49 89 38 8b 73 14 8b 7b 0c e8 18 f6 ff ff 49 b8 5b e3 74 9d 02 11 f9 09 4c 89 00 44 8b 7b 14 44 89 f8 e9 fa fe ff ff 0f 0b <0f> 0b 48 8b 40 30 e9 d9 fe ff ff e8 c6 43 3b 00 0f 0b 48 8b 40 
[   52.810032] RIP  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032]  RSP <ffff88003eaf3bc0>
[   52.810032] ---[ end trace c699c8cecd5870a3 ]---


And other times, I see a filesystem related slab corruption when doing the eject.
Here I have also seen a bad rss-counter state message. 

[  232.114232] BUG: Bad rss-counter state mm:ffff88007d9c1f80 idx:0 val:1
[  232.115214] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  232.115807] IP: [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.116186] PGD 7cdec067 PUD 7c946067 PMD 0 
[  232.116627] Oops: 0000 [#3] SMP 
[  232.116990] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor thermal_sys button ext3 jbd mbcache virtio_net sg sr_mod cdrom virtio_blk ata_generic virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[  232.120013] CPU 2 
[  232.120013] Pid: 880, comm: dhclient Tainted: G      D      3.6.0-rc7-guest #1 Bochs Bochs
[  232.120013] RIP: 0010:[<ffffffffa00cfce3>]  [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.120013] RSP: 0018:ffff88007cd6fab8  EFLAGS: 00010246
[  232.120013] RAX: ffff88003e513f50 RBX: ffff88003e513f50 RCX: 0000000000000000
[  232.120013] RDX: 0000000000000000 RSI: ffff88003e513f50 RDI: ffff880097800000
[  232.120013] RBP: ffff88003e513f50 R08: 000000003e513f01 R09: 0000000180240024
[  232.120013] R10: ffff88003e513f50 R11: 00000000000198e0 R12: 0000000000000000
[  232.120013] R13: ffffffffa00eb437 R14: ffff880097800000 R15: 000000000000027a
[  232.120013] FS:  00007f082638d700(0000) GS:ffff88003ec80000(0000) knlGS:0000000000000000
[  232.120013] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  232.120013] CR2: 0000000000000000 CR3: 000000007c94c000 CR4: 00000000000006e0
[  232.120013] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  232.120013] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  232.120013] Process dhclient (pid: 880, threadinfo ffff88007cd6e000, task ffff88007ca46800)
[  232.120013] Stack:
[  232.120013]  ffff88007dc205b0 ffffffff8116645f ffff88007dc205b0 ffff88007dc205b0
[  232.120013]  ffff88007cf58800 0000000000000000 000000000000000e 0000000000000000
[  232.120013]  000000000000027a ffffffff8112b934 0000005000000003 0000000000000fff
[  232.120013] Call Trace:
[  232.120013]  [<ffffffff8116645f>] ? __find_get_block+0x7f/0x200
[  232.120013]  [<ffffffff8112b934>] ? kmem_cache_alloc+0xe4/0x140
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffffa00d0279>] ? journal_get_write_access+0x29/0x50 [jbd]
[  232.120013]  [<ffffffffa00eaeef>] ? __ext3_get_inode_loc+0xcf/0x360 [ext3]
[  232.120013]  [<ffffffffa0101317>] ? __ext3_journal_get_write_access+0x27/0x60 [ext3]
[  232.120013]  [<ffffffffa00eb213>] ? ext3_reserve_inode_write+0x73/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb27b>] ? ext3_mark_inode_dirty+0x3b/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffff8115ded6>] ? __mark_inode_dirty+0x36/0x230
[  232.120013]  [<ffffffff811504a1>] ? update_time+0x71/0xb0
[  232.120013]  [<ffffffff811536c9>] ? mnt_clone_write+0x9/0x20
[  232.120013]  [<ffffffff81150581>] ? file_update_time+0xa1/0xf0
[  232.120013]  [<ffffffff8103385c>] ? ptep_set_access_flags+0x6c/0x70
[  232.120013]  [<ffffffff810e3f30>] ? __generic_file_aio_write+0x1a0/0x3c0
[  232.120013]  [<ffffffff811396fb>] ? __sb_start_write+0x6b/0x130
[  232.120013]  [<ffffffff810e41ce>] ? generic_file_aio_write+0x7e/0x100
[  232.120013]  [<ffffffff81137484>] ? do_sync_write+0x94/0xd0
[  232.120013]  [<ffffffff81137caa>] ? vfs_write+0xaa/0x160
[  232.120013]  [<ffffffff81137f87>] ? sys_write+0x47/0x90
[  232.120013]  [<ffffffff814e5765>] ? async_page_fault+0x25/0x30
[  232.120013]  [<ffffffff814eca79>] ? system_call_fastpath+0x16/0x1b
[  232.120013] Code: 54 24 2c f6 47 14 04 74 1f 41 bc e2 ff ff ff 48 81 c4 98 00 00 00 44 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 4c 8b 27 <4d> 8b 3c 24 41 f6 07 02 75 d4 65 48 8b 04 25 80 b9 00 00 48 89 

Is this a known issue? If yes, can you point me to any relevant patches?

When I do an SCI(hardware) eject, I have not seen corruptions. The acpi driver is
evaluating fewer objects in this path I think, but I don't see why corruption can't
happen here as well.

I have seen similar problems with CONFIG_SLUB (I did not have debug_options
there but I can also provide those if helpful)

[1] https://lkml.org/lkml/2012/9/6/635
[2] https://lkml.org/lkml/2012/9/11/542
[3] https://lkml.org/lkml/2012/9/20/37
[4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691

thanks,

- Vasilis

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Vasilis Liaskovitis <hidden>
Date: 2012-09-26 16:58:34

Testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

- succesfull hot-add and online
- succesfull hot-remove with SCI (qemu) eject
- attempt to hot-readd same memory

When the pages are re-onlined on hot-readd, I get a bad_page state for many
pages e.g.

[   59.611278] init_memory_mapping: [mem 0x80000000-0x9fffffff]
[   59.637836] Built 2 zonelists in Node order, mobility grouping on.  Total pages: 547617
[   59.638739] Policy zone: Normal
[   59.650840] BUG: Bad page state in process bash  pfn:9b6dc
[   59.651124] page:ffffea0002200020 count:0 mapcount:0 mapping:          (null) index:0xfdfdfdfdfdfdfdfd
[   59.651494] page flags: 0x2fdfdfdfd5df9fd(locked|referenced|uptodate|dirty|lru|active|slab|owner_priv_1|private|private_2|writeback|head|tail|swapcache|reclaim|swapbacked|unevictable|uncached|compound_lock)
[   59.653604] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor button thermal_sys ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net ata_piix virtio_blk libata virtio_pci virtio_ring virtio scsi_mod
[   59.656998] Pid: 988, comm: bash Not tainted 3.6.0-rc7-guest #12
[   59.657172] Call Trace:
[   59.657275]  [<ffffffff810e9b30>] ? bad_page+0xb0/0x100
[   59.657434]  [<ffffffff810ea4c3>] ? free_pages_prepare+0xb3/0x100
[   59.657610]  [<ffffffff810ea668>] ? free_hot_cold_page+0x48/0x1a0
[   59.657787]  [<ffffffff8112cc08>] ? online_pages_range+0x68/0xa0
[   59.657961]  [<ffffffff8112cba0>] ? __online_page_increment_counters+0x10/0x10
[   59.658162]  [<ffffffff81045561>] ? walk_system_ram_range+0x101/0x110
[   59.658346]  [<ffffffff814c4f95>] ? online_pages+0x1a5/0x2b0
[   59.658515]  [<ffffffff8135663d>] ? __memory_block_change_state+0x20d/0x270
[   59.658710]  [<ffffffff81356756>] ? store_mem_state+0xb6/0xf0
[   59.658878]  [<ffffffff8119e482>] ? sysfs_write_file+0xd2/0x160
[   59.659052]  [<ffffffff8113769a>] ? vfs_write+0xaa/0x160
[   59.659212]  [<ffffffff81137977>] ? sys_write+0x47/0x90
[   59.659371]  [<ffffffff814e2f25>] ? async_page_fault+0x25/0x30
[   59.659543]  [<ffffffff814ea239>] ? system_call_fastpath+0x16/0x1b
[   59.659720] Disabling lock debugging due to kernel taint

Patch 20/21 deals with a similar scenario, but only for __PG_HWPOISON flag.
Did i miss any other patch for this?

thanks,

- Vasilis

[1] https://lkml.org/lkml/2012/9/6/635
[2] https://lkml.org/lkml/2012/9/11/542
[3] https://lkml.org/lkml/2012/9/20/37
[4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Wen Congyang <hidden>
Date: 2012-09-27 00:54:18

At 09/27/2012 12:46 AM, Vasilis Liaskovitis Wrote:
Hi,

I am testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

After succesfull hot-add and online, I am doing a hot-remove with "echo 1 > /sys/bus/acpi/devices/PNP/eject"
When I do the OSPM-eject, I often get slab corruption in "acpi-state" cache, or in other caches

[  170.566995] Slab corruption (Not tainted): Acpi-State start=ffff88009fc1e548, len=80
[  170.567265] Redzone: 0x0/0x0.
[  170.567399] Last user: [<          (null)>](0x0)
[  170.567667] 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568078] 010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568487] 020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568894] 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569302] 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569712] Prev obj: start=000000009fc1e4d0, len=80
[  170.569869] BUG: unable to handle kernel paging request at 000000009fc1e520
[  170.570171] IP: [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.570397] PGD 7cf37067 PUD 0 
[  170.570619] Oops: 0000 [#1] SMP 
[  170.570843] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis microcode tpm tpm_bios psmouse parport_pc serio_raw evdev parport i2c_piix4 processor thermal_sys i2c_core button ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net virtio_blk ata_piix libata scsi_mod virtio_pci virtio_ring virtio
[  170.573474] CPU 0 
[  170.573568] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[  170.573830] RIP: 0010:[<ffffffff8112803c>]  [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.574106] RSP: 0018:ffff88003eaf3a70  EFLAGS: 00010202
[  170.574268] RAX: 000000009fc1e4c8 RBX: 0000000000000002 RCX: 00000000000024b8
[  170.574468] RDX: 000000009fc1e4c8 RSI: 000000009fc1e4c8 RDI: ffff88003e9bb980
[  170.574668] RBP: ffff88003e9bb980 R08: ffff880037964078 R09: 0000000000000000
[  170.574870] R10: 000000000000021e R11: 0000000000000002 R12: 000000009fc1e4c8
[  170.575070] R13: 000000009fc1e520 R14: 000000000000004f R15: 00000000ffffffa5
[  170.575274] FS:  00007fc6b7530700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[  170.575494] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  170.575665] CR2: 000000009fc1e520 CR3: 000000007c9c1000 CR4: 00000000000006f0
[  170.575870] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  170.576075] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  170.576276] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[  170.576507] Stack:
[  170.576599]  0000000000000010 0000000001893fbe ffff88009fc1e000 0000000000000050
[  170.576938]  000000009fc1e4c8 000000000000004f 00000000ffffffa5 ffffffff8112899f
[  170.576938]  ffff88003eb309d8 ffffffff81712d6d ffff88003e9bb980 ffff88009fc1e540
[  170.576938] Call Trace:
[  170.576938]  [<ffffffff8112899f>] ? check_poison_obj+0x1df/0x1f0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff81128a9d>] ? cache_alloc_debugcheck_after.isra.52+0xed/0x220
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff8112beb5>] ? kmem_cache_alloc+0xb5/0x1e0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff812edf2d>] ? acpi_ds_result_push+0x5d/0x12e
[  170.576938]  [<ffffffff812ed127>] ? acpi_ds_exec_end_op+0x28e/0x3d3
[  170.576938]  [<ffffffff812fd86a>] ? acpi_ps_parse_loop+0x79f/0x931
[  170.576938]  [<ffffffff812fdd6c>] ? acpi_ps_parse_aml+0x89/0x261
[  170.576938]  [<ffffffff812fe50c>] ? acpi_ps_execute_method+0x1be/0x266
[  170.576938]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[  170.576938]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[  170.576938]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[  170.576938]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[  170.576938]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[  170.576938]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[  170.576938]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[  170.576938]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[  170.576938]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[  170.576938]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[  170.576938]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[  170.576938]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[  170.576938] Code: cb 75 dc 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 8b 7f 0c 4c 89 e2 e8 02 fd ff ff 4c 89 e6 49 89 c5 48 89 ef e8 d4 fc ff ff <49> 8b 55 00 48 8b 30 48 c7 c7 8c 39 6f 81 31 c0 e8 3e 34 3b 00 

Other times, the problem happens on a slab object free:

[   52.313366] Offlined Pages 32768
[   52.800232] slab error in verify_redzone_free(): cache `Acpi-ParseExt': memory outside object was overwritten
[   52.801298] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12
[   52.802039] Call Trace:
[   52.802443]  [<ffffffff811280cb>] ? __slab_error.isra.46+0x1b/0x30
[   52.803199]  [<ffffffff811287b6>] ? cache_free_debugcheck+0x256/0x260
[   52.803940]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.804645]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.805321]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.806023]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.806762]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.807499]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.808183]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.808897]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.809659]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] ffff88008f809670: redzone 1:0x0, redzone 2:0x0.
[   52.810032] ------------[ cut here ]------------
[   52.810032] kernel BUG at mm/slab.c:3125!
[   52.810032] invalid opcode: 0000 [#1] SMP 
[   52.810032] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis tpm tpm_bios microcode parport_pc parport evdev processor thermal_sys psmouse i2c_piix4 serio_raw i2c_core button ext3 jbd mbcache sg sr_mod cdrom virtio_net ata_generic virtio_blk virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[   52.810032] CPU 0 
[   52.810032] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[   52.810032] RIP: 0010:[<ffffffff81128733>]  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032] RSP: 0018:ffff88003eaf3bc0  EFLAGS: 00010093
[   52.810032] RAX: 00000000017eac3c RBX: ffff88003e9bb700 RCX: 0000000002aaaaab
[   52.810032] RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000060
[   52.810032] RBP: ffff88008f809670 R08: 09f911029d74e35b R09: 0000000000000000
[   52.810032] R10: 00000000000001d3 R11: 0000000000000002 R12: ffff88008f809000
[   52.810032] R13: ffffffff812e1b0e R14: 0000000000000000 R15: 0000000000010c00
[   52.810032] FS:  00007f63fc263700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[   52.810032] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   52.810032] CR2: 00007fff8d895b78 CR3: 000000007c866000 CR4: 00000000000006f0
[   52.810032] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   52.810032] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   52.810032] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[   52.810032] Stack:
[   52.810032]  ffff88003e9bb980 ffff88008f809670 ffff880037ba8e18 ffff88008f809678
[   52.810032]  ffff88003e9bb700 0000000000000282 ffff88003e9bf270 ffffffff812e1b0e
[   52.810032]  0000000000000001 ffffffff81128fe3 ffff88003e80f5e8 ffff88003eb31748
[   52.810032] Call Trace:
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.810032]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.810032]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.810032]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.810032]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.810032]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] Code: 89 ea 49 89 38 8b 73 14 8b 7b 0c e8 18 f6 ff ff 49 b8 5b e3 74 9d 02 11 f9 09 4c 89 00 44 8b 7b 14 44 89 f8 e9 fa fe ff ff 0f 0b <0f> 0b 48 8b 40 30 e9 d9 fe ff ff e8 c6 43 3b 00 0f 0b 48 8b 40 
[   52.810032] RIP  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032]  RSP <ffff88003eaf3bc0>
[   52.810032] ---[ end trace c699c8cecd5870a3 ]---


And other times, I see a filesystem related slab corruption when doing the eject.
Here I have also seen a bad rss-counter state message. 

[  232.114232] BUG: Bad rss-counter state mm:ffff88007d9c1f80 idx:0 val:1
[  232.115214] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  232.115807] IP: [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.116186] PGD 7cdec067 PUD 7c946067 PMD 0 
[  232.116627] Oops: 0000 [#3] SMP 
[  232.116990] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor thermal_sys button ext3 jbd mbcache virtio_net sg sr_mod cdrom virtio_blk ata_generic virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[  232.120013] CPU 2 
[  232.120013] Pid: 880, comm: dhclient Tainted: G      D      3.6.0-rc7-guest #1 Bochs Bochs
[  232.120013] RIP: 0010:[<ffffffffa00cfce3>]  [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.120013] RSP: 0018:ffff88007cd6fab8  EFLAGS: 00010246
[  232.120013] RAX: ffff88003e513f50 RBX: ffff88003e513f50 RCX: 0000000000000000
[  232.120013] RDX: 0000000000000000 RSI: ffff88003e513f50 RDI: ffff880097800000
[  232.120013] RBP: ffff88003e513f50 R08: 000000003e513f01 R09: 0000000180240024
[  232.120013] R10: ffff88003e513f50 R11: 00000000000198e0 R12: 0000000000000000
[  232.120013] R13: ffffffffa00eb437 R14: ffff880097800000 R15: 000000000000027a
[  232.120013] FS:  00007f082638d700(0000) GS:ffff88003ec80000(0000) knlGS:0000000000000000
[  232.120013] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  232.120013] CR2: 0000000000000000 CR3: 000000007c94c000 CR4: 00000000000006e0
[  232.120013] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  232.120013] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  232.120013] Process dhclient (pid: 880, threadinfo ffff88007cd6e000, task ffff88007ca46800)
[  232.120013] Stack:
[  232.120013]  ffff88007dc205b0 ffffffff8116645f ffff88007dc205b0 ffff88007dc205b0
[  232.120013]  ffff88007cf58800 0000000000000000 000000000000000e 0000000000000000
[  232.120013]  000000000000027a ffffffff8112b934 0000005000000003 0000000000000fff
[  232.120013] Call Trace:
[  232.120013]  [<ffffffff8116645f>] ? __find_get_block+0x7f/0x200
[  232.120013]  [<ffffffff8112b934>] ? kmem_cache_alloc+0xe4/0x140
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffffa00d0279>] ? journal_get_write_access+0x29/0x50 [jbd]
[  232.120013]  [<ffffffffa00eaeef>] ? __ext3_get_inode_loc+0xcf/0x360 [ext3]
[  232.120013]  [<ffffffffa0101317>] ? __ext3_journal_get_write_access+0x27/0x60 [ext3]
[  232.120013]  [<ffffffffa00eb213>] ? ext3_reserve_inode_write+0x73/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb27b>] ? ext3_mark_inode_dirty+0x3b/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffff8115ded6>] ? __mark_inode_dirty+0x36/0x230
[  232.120013]  [<ffffffff811504a1>] ? update_time+0x71/0xb0
[  232.120013]  [<ffffffff811536c9>] ? mnt_clone_write+0x9/0x20
[  232.120013]  [<ffffffff81150581>] ? file_update_time+0xa1/0xf0
[  232.120013]  [<ffffffff8103385c>] ? ptep_set_access_flags+0x6c/0x70
[  232.120013]  [<ffffffff810e3f30>] ? __generic_file_aio_write+0x1a0/0x3c0
[  232.120013]  [<ffffffff811396fb>] ? __sb_start_write+0x6b/0x130
[  232.120013]  [<ffffffff810e41ce>] ? generic_file_aio_write+0x7e/0x100
[  232.120013]  [<ffffffff81137484>] ? do_sync_write+0x94/0xd0
[  232.120013]  [<ffffffff81137caa>] ? vfs_write+0xaa/0x160
[  232.120013]  [<ffffffff81137f87>] ? sys_write+0x47/0x90
[  232.120013]  [<ffffffff814e5765>] ? async_page_fault+0x25/0x30
[  232.120013]  [<ffffffff814eca79>] ? system_call_fastpath+0x16/0x1b
[  232.120013] Code: 54 24 2c f6 47 14 04 74 1f 41 bc e2 ff ff ff 48 81 c4 98 00 00 00 44 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 4c 8b 27 <4d> 8b 3c 24 41 f6 07 02 75 d4 65 48 8b 04 25 80 b9 00 00 48 89 

Is this a known issue? If yes, can you point me to any relevant patches?

When I do an SCI(hardware) eject, I have not seen corruptions. The acpi driver is
evaluating fewer objects in this path I think, but I don't see why corruption can't
happen here as well.

I have seen similar problems with CONFIG_SLUB (I did not have debug_options
there but I can also provide those if helpful)
Thanks for testing it.
It is not a know issue. I will start to investigate it.

Wen Congyang
[1] https://lkml.org/lkml/2012/9/6/635
[2] https://lkml.org/lkml/2012/9/11/542
[3] https://lkml.org/lkml/2012/9/20/37
[4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691

thanks,

- Vasilis

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Wen Congyang <hidden>
Date: 2012-09-27 00:58:11

At 09/27/2012 12:58 AM, Vasilis Liaskovitis Wrote:
Testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

- succesfull hot-add and online
- succesfull hot-remove with SCI (qemu) eject
- attempt to hot-readd same memory

When the pages are re-onlined on hot-readd, I get a bad_page state for many
pages e.g.
Can you provide your config file?

Thanks
Wen Congyang
[   59.611278] init_memory_mapping: [mem 0x80000000-0x9fffffff]
[   59.637836] Built 2 zonelists in Node order, mobility grouping on.  Total pages: 547617
[   59.638739] Policy zone: Normal
[   59.650840] BUG: Bad page state in process bash  pfn:9b6dc
[   59.651124] page:ffffea0002200020 count:0 mapcount:0 mapping:          (null) index:0xfdfdfdfdfdfdfdfd
[   59.651494] page flags: 0x2fdfdfdfd5df9fd(locked|referenced|uptodate|dirty|lru|active|slab|owner_priv_1|private|private_2|writeback|head|tail|swapcache|reclaim|swapbacked|unevictable|uncached|compound_lock)
[   59.653604] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor button thermal_sys ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net ata_piix virtio_blk libata virtio_pci virtio_ring virtio scsi_mod
[   59.656998] Pid: 988, comm: bash Not tainted 3.6.0-rc7-guest #12
[   59.657172] Call Trace:
[   59.657275]  [<ffffffff810e9b30>] ? bad_page+0xb0/0x100
[   59.657434]  [<ffffffff810ea4c3>] ? free_pages_prepare+0xb3/0x100
[   59.657610]  [<ffffffff810ea668>] ? free_hot_cold_page+0x48/0x1a0
[   59.657787]  [<ffffffff8112cc08>] ? online_pages_range+0x68/0xa0
[   59.657961]  [<ffffffff8112cba0>] ? __online_page_increment_counters+0x10/0x10
[   59.658162]  [<ffffffff81045561>] ? walk_system_ram_range+0x101/0x110
[   59.658346]  [<ffffffff814c4f95>] ? online_pages+0x1a5/0x2b0
[   59.658515]  [<ffffffff8135663d>] ? __memory_block_change_state+0x20d/0x270
[   59.658710]  [<ffffffff81356756>] ? store_mem_state+0xb6/0xf0
[   59.658878]  [<ffffffff8119e482>] ? sysfs_write_file+0xd2/0x160
[   59.659052]  [<ffffffff8113769a>] ? vfs_write+0xaa/0x160
[   59.659212]  [<ffffffff81137977>] ? sys_write+0x47/0x90
[   59.659371]  [<ffffffff814e2f25>] ? async_page_fault+0x25/0x30
[   59.659543]  [<ffffffff814ea239>] ? system_call_fastpath+0x16/0x1b
[   59.659720] Disabling lock debugging due to kernel taint

Patch 20/21 deals with a similar scenario, but only for __PG_HWPOISON flag.
Did i miss any other patch for this?

thanks,

- Vasilis

[1] https://lkml.org/lkml/2012/9/6/635
[2] https://lkml.org/lkml/2012/9/11/542
[3] https://lkml.org/lkml/2012/9/20/37
[4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Wen Congyang <hidden>
Date: 2012-09-27 06:31:46

Hi Vasilis Liaskovitis

At 09/27/2012 12:46 AM, Vasilis Liaskovitis Wrote:
Hi,

I am testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

After succesfull hot-add and online, I am doing a hot-remove with "echo 1 > /sys/bus/acpi/devices/PNP/eject"
When I do the OSPM-eject, I often get slab corruption in "acpi-state" cache, or in other caches
I can't reproduce this problem. Can you provide the following information:
1. config file
2. qemu's command line

You said you did OSPM-eject. Do you mean write 1 to /sys/bus/acpi/devices/PNP0C80:XX/eject?

Thanks
Wen Congyang
[  170.566995] Slab corruption (Not tainted): Acpi-State start=ffff88009fc1e548, len=80
[  170.567265] Redzone: 0x0/0x0.
[  170.567399] Last user: [<          (null)>](0x0)
[  170.567667] 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568078] 010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568487] 020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568894] 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569302] 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569712] Prev obj: start=000000009fc1e4d0, len=80
[  170.569869] BUG: unable to handle kernel paging request at 000000009fc1e520
[  170.570171] IP: [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.570397] PGD 7cf37067 PUD 0 
[  170.570619] Oops: 0000 [#1] SMP 
[  170.570843] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis microcode tpm tpm_bios psmouse parport_pc serio_raw evdev parport i2c_piix4 processor thermal_sys i2c_core button ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net virtio_blk ata_piix libata scsi_mod virtio_pci virtio_ring virtio
[  170.573474] CPU 0 
[  170.573568] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[  170.573830] RIP: 0010:[<ffffffff8112803c>]  [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.574106] RSP: 0018:ffff88003eaf3a70  EFLAGS: 00010202
[  170.574268] RAX: 000000009fc1e4c8 RBX: 0000000000000002 RCX: 00000000000024b8
[  170.574468] RDX: 000000009fc1e4c8 RSI: 000000009fc1e4c8 RDI: ffff88003e9bb980
[  170.574668] RBP: ffff88003e9bb980 R08: ffff880037964078 R09: 0000000000000000
[  170.574870] R10: 000000000000021e R11: 0000000000000002 R12: 000000009fc1e4c8
[  170.575070] R13: 000000009fc1e520 R14: 000000000000004f R15: 00000000ffffffa5
[  170.575274] FS:  00007fc6b7530700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[  170.575494] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  170.575665] CR2: 000000009fc1e520 CR3: 000000007c9c1000 CR4: 00000000000006f0
[  170.575870] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  170.576075] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  170.576276] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[  170.576507] Stack:
[  170.576599]  0000000000000010 0000000001893fbe ffff88009fc1e000 0000000000000050
[  170.576938]  000000009fc1e4c8 000000000000004f 00000000ffffffa5 ffffffff8112899f
[  170.576938]  ffff88003eb309d8 ffffffff81712d6d ffff88003e9bb980 ffff88009fc1e540
[  170.576938] Call Trace:
[  170.576938]  [<ffffffff8112899f>] ? check_poison_obj+0x1df/0x1f0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff81128a9d>] ? cache_alloc_debugcheck_after.isra.52+0xed/0x220
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff8112beb5>] ? kmem_cache_alloc+0xb5/0x1e0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff812edf2d>] ? acpi_ds_result_push+0x5d/0x12e
[  170.576938]  [<ffffffff812ed127>] ? acpi_ds_exec_end_op+0x28e/0x3d3
[  170.576938]  [<ffffffff812fd86a>] ? acpi_ps_parse_loop+0x79f/0x931
[  170.576938]  [<ffffffff812fdd6c>] ? acpi_ps_parse_aml+0x89/0x261
[  170.576938]  [<ffffffff812fe50c>] ? acpi_ps_execute_method+0x1be/0x266
[  170.576938]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[  170.576938]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[  170.576938]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[  170.576938]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[  170.576938]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[  170.576938]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[  170.576938]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[  170.576938]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[  170.576938]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[  170.576938]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[  170.576938]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[  170.576938]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[  170.576938] Code: cb 75 dc 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 8b 7f 0c 4c 89 e2 e8 02 fd ff ff 4c 89 e6 49 89 c5 48 89 ef e8 d4 fc ff ff <49> 8b 55 00 48 8b 30 48 c7 c7 8c 39 6f 81 31 c0 e8 3e 34 3b 00 

Other times, the problem happens on a slab object free:

[   52.313366] Offlined Pages 32768
[   52.800232] slab error in verify_redzone_free(): cache `Acpi-ParseExt': memory outside object was overwritten
[   52.801298] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12
[   52.802039] Call Trace:
[   52.802443]  [<ffffffff811280cb>] ? __slab_error.isra.46+0x1b/0x30
[   52.803199]  [<ffffffff811287b6>] ? cache_free_debugcheck+0x256/0x260
[   52.803940]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.804645]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.805321]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.806023]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.806762]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.807499]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.808183]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.808897]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.809659]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] ffff88008f809670: redzone 1:0x0, redzone 2:0x0.
[   52.810032] ------------[ cut here ]------------
[   52.810032] kernel BUG at mm/slab.c:3125!
[   52.810032] invalid opcode: 0000 [#1] SMP 
[   52.810032] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis tpm tpm_bios microcode parport_pc parport evdev processor thermal_sys psmouse i2c_piix4 serio_raw i2c_core button ext3 jbd mbcache sg sr_mod cdrom virtio_net ata_generic virtio_blk virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[   52.810032] CPU 0 
[   52.810032] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[   52.810032] RIP: 0010:[<ffffffff81128733>]  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032] RSP: 0018:ffff88003eaf3bc0  EFLAGS: 00010093
[   52.810032] RAX: 00000000017eac3c RBX: ffff88003e9bb700 RCX: 0000000002aaaaab
[   52.810032] RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000060
[   52.810032] RBP: ffff88008f809670 R08: 09f911029d74e35b R09: 0000000000000000
[   52.810032] R10: 00000000000001d3 R11: 0000000000000002 R12: ffff88008f809000
[   52.810032] R13: ffffffff812e1b0e R14: 0000000000000000 R15: 0000000000010c00
[   52.810032] FS:  00007f63fc263700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[   52.810032] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   52.810032] CR2: 00007fff8d895b78 CR3: 000000007c866000 CR4: 00000000000006f0
[   52.810032] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   52.810032] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   52.810032] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[   52.810032] Stack:
[   52.810032]  ffff88003e9bb980 ffff88008f809670 ffff880037ba8e18 ffff88008f809678
[   52.810032]  ffff88003e9bb700 0000000000000282 ffff88003e9bf270 ffffffff812e1b0e
[   52.810032]  0000000000000001 ffffffff81128fe3 ffff88003e80f5e8 ffff88003eb31748
[   52.810032] Call Trace:
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.810032]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.810032]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.810032]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.810032]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.810032]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] Code: 89 ea 49 89 38 8b 73 14 8b 7b 0c e8 18 f6 ff ff 49 b8 5b e3 74 9d 02 11 f9 09 4c 89 00 44 8b 7b 14 44 89 f8 e9 fa fe ff ff 0f 0b <0f> 0b 48 8b 40 30 e9 d9 fe ff ff e8 c6 43 3b 00 0f 0b 48 8b 40 
[   52.810032] RIP  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032]  RSP <ffff88003eaf3bc0>
[   52.810032] ---[ end trace c699c8cecd5870a3 ]---


And other times, I see a filesystem related slab corruption when doing the eject.
Here I have also seen a bad rss-counter state message. 

[  232.114232] BUG: Bad rss-counter state mm:ffff88007d9c1f80 idx:0 val:1
[  232.115214] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  232.115807] IP: [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.116186] PGD 7cdec067 PUD 7c946067 PMD 0 
[  232.116627] Oops: 0000 [#3] SMP 
[  232.116990] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor thermal_sys button ext3 jbd mbcache virtio_net sg sr_mod cdrom virtio_blk ata_generic virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[  232.120013] CPU 2 
[  232.120013] Pid: 880, comm: dhclient Tainted: G      D      3.6.0-rc7-guest #1 Bochs Bochs
[  232.120013] RIP: 0010:[<ffffffffa00cfce3>]  [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.120013] RSP: 0018:ffff88007cd6fab8  EFLAGS: 00010246
[  232.120013] RAX: ffff88003e513f50 RBX: ffff88003e513f50 RCX: 0000000000000000
[  232.120013] RDX: 0000000000000000 RSI: ffff88003e513f50 RDI: ffff880097800000
[  232.120013] RBP: ffff88003e513f50 R08: 000000003e513f01 R09: 0000000180240024
[  232.120013] R10: ffff88003e513f50 R11: 00000000000198e0 R12: 0000000000000000
[  232.120013] R13: ffffffffa00eb437 R14: ffff880097800000 R15: 000000000000027a
[  232.120013] FS:  00007f082638d700(0000) GS:ffff88003ec80000(0000) knlGS:0000000000000000
[  232.120013] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  232.120013] CR2: 0000000000000000 CR3: 000000007c94c000 CR4: 00000000000006e0
[  232.120013] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  232.120013] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  232.120013] Process dhclient (pid: 880, threadinfo ffff88007cd6e000, task ffff88007ca46800)
[  232.120013] Stack:
[  232.120013]  ffff88007dc205b0 ffffffff8116645f ffff88007dc205b0 ffff88007dc205b0
[  232.120013]  ffff88007cf58800 0000000000000000 000000000000000e 0000000000000000
[  232.120013]  000000000000027a ffffffff8112b934 0000005000000003 0000000000000fff
[  232.120013] Call Trace:
[  232.120013]  [<ffffffff8116645f>] ? __find_get_block+0x7f/0x200
[  232.120013]  [<ffffffff8112b934>] ? kmem_cache_alloc+0xe4/0x140
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffffa00d0279>] ? journal_get_write_access+0x29/0x50 [jbd]
[  232.120013]  [<ffffffffa00eaeef>] ? __ext3_get_inode_loc+0xcf/0x360 [ext3]
[  232.120013]  [<ffffffffa0101317>] ? __ext3_journal_get_write_access+0x27/0x60 [ext3]
[  232.120013]  [<ffffffffa00eb213>] ? ext3_reserve_inode_write+0x73/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb27b>] ? ext3_mark_inode_dirty+0x3b/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffff8115ded6>] ? __mark_inode_dirty+0x36/0x230
[  232.120013]  [<ffffffff811504a1>] ? update_time+0x71/0xb0
[  232.120013]  [<ffffffff811536c9>] ? mnt_clone_write+0x9/0x20
[  232.120013]  [<ffffffff81150581>] ? file_update_time+0xa1/0xf0
[  232.120013]  [<ffffffff8103385c>] ? ptep_set_access_flags+0x6c/0x70
[  232.120013]  [<ffffffff810e3f30>] ? __generic_file_aio_write+0x1a0/0x3c0
[  232.120013]  [<ffffffff811396fb>] ? __sb_start_write+0x6b/0x130
[  232.120013]  [<ffffffff810e41ce>] ? generic_file_aio_write+0x7e/0x100
[  232.120013]  [<ffffffff81137484>] ? do_sync_write+0x94/0xd0
[  232.120013]  [<ffffffff81137caa>] ? vfs_write+0xaa/0x160
[  232.120013]  [<ffffffff81137f87>] ? sys_write+0x47/0x90
[  232.120013]  [<ffffffff814e5765>] ? async_page_fault+0x25/0x30
[  232.120013]  [<ffffffff814eca79>] ? system_call_fastpath+0x16/0x1b
[  232.120013] Code: 54 24 2c f6 47 14 04 74 1f 41 bc e2 ff ff ff 48 81 c4 98 00 00 00 44 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 4c 8b 27 <4d> 8b 3c 24 41 f6 07 02 75 d4 65 48 8b 04 25 80 b9 00 00 48 89 

Is this a known issue? If yes, can you point me to any relevant patches?

When I do an SCI(hardware) eject, I have not seen corruptions. The acpi driver is
evaluating fewer objects in this path I think, but I don't see why corruption can't
happen here as well.

I have seen similar problems with CONFIG_SLUB (I did not have debug_options
there but I can also provide those if helpful)

[1] https://lkml.org/lkml/2012/9/6/635
[2] https://lkml.org/lkml/2012/9/11/542
[3] https://lkml.org/lkml/2012/9/20/37
[4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691

thanks,

- Vasilis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Wen Congyang <hidden>
Date: 2012-09-27 08:48:23

At 09/27/2012 12:58 AM, Vasilis Liaskovitis Wrote:
Testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

- succesfull hot-add and online
- succesfull hot-remove with SCI (qemu) eject
- attempt to hot-readd same memory

When the pages are re-onlined on hot-readd, I get a bad_page state for many
pages e.g.
I have reproduced this problem, and I investigate it now.

Thanks
Wen Congyang
[   59.611278] init_memory_mapping: [mem 0x80000000-0x9fffffff]
[   59.637836] Built 2 zonelists in Node order, mobility grouping on.  Total pages: 547617
[   59.638739] Policy zone: Normal
[   59.650840] BUG: Bad page state in process bash  pfn:9b6dc
[   59.651124] page:ffffea0002200020 count:0 mapcount:0 mapping:          (null) index:0xfdfdfdfdfdfdfdfd
[   59.651494] page flags: 0x2fdfdfdfd5df9fd(locked|referenced|uptodate|dirty|lru|active|slab|owner_priv_1|private|private_2|writeback|head|tail|swapcache|reclaim|swapbacked|unevictable|uncached|compound_lock)
[   59.653604] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor button thermal_sys ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net ata_piix virtio_blk libata virtio_pci virtio_ring virtio scsi_mod
[   59.656998] Pid: 988, comm: bash Not tainted 3.6.0-rc7-guest #12
[   59.657172] Call Trace:
[   59.657275]  [<ffffffff810e9b30>] ? bad_page+0xb0/0x100
[   59.657434]  [<ffffffff810ea4c3>] ? free_pages_prepare+0xb3/0x100
[   59.657610]  [<ffffffff810ea668>] ? free_hot_cold_page+0x48/0x1a0
[   59.657787]  [<ffffffff8112cc08>] ? online_pages_range+0x68/0xa0
[   59.657961]  [<ffffffff8112cba0>] ? __online_page_increment_counters+0x10/0x10
[   59.658162]  [<ffffffff81045561>] ? walk_system_ram_range+0x101/0x110
[   59.658346]  [<ffffffff814c4f95>] ? online_pages+0x1a5/0x2b0
[   59.658515]  [<ffffffff8135663d>] ? __memory_block_change_state+0x20d/0x270
[   59.658710]  [<ffffffff81356756>] ? store_mem_state+0xb6/0xf0
[   59.658878]  [<ffffffff8119e482>] ? sysfs_write_file+0xd2/0x160
[   59.659052]  [<ffffffff8113769a>] ? vfs_write+0xaa/0x160
[   59.659212]  [<ffffffff81137977>] ? sys_write+0x47/0x90
[   59.659371]  [<ffffffff814e2f25>] ? async_page_fault+0x25/0x30
[   59.659543]  [<ffffffff814ea239>] ? system_call_fastpath+0x16/0x1b
[   59.659720] Disabling lock debugging due to kernel taint

Patch 20/21 deals with a similar scenario, but only for __PG_HWPOISON flag.
Did i miss any other patch for this?

thanks,

- Vasilis

[1] https://lkml.org/lkml/2012/9/6/635
[2] https://lkml.org/lkml/2012/9/11/542
[3] https://lkml.org/lkml/2012/9/20/37
[4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Wen Congyang <hidden>
Date: 2012-09-27 10:00:52

At 09/27/2012 12:58 AM, Vasilis Liaskovitis Wrote:
Testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

- succesfull hot-add and online
- succesfull hot-remove with SCI (qemu) eject
- attempt to hot-readd same memory

When the pages are re-onlined on hot-readd, I get a bad_page state for many
pages e.g.

[   59.611278] init_memory_mapping: [mem 0x80000000-0x9fffffff]
[   59.637836] Built 2 zonelists in Node order, mobility grouping on.  Total pages: 547617
[   59.638739] Policy zone: Normal
[   59.650840] BUG: Bad page state in process bash  pfn:9b6dc
[   59.651124] page:ffffea0002200020 count:0 mapcount:0 mapping:          (null) index:0xfdfdfdfdfdfdfdfd
[   59.651494] page flags: 0x2fdfdfdfd5df9fd(locked|referenced|uptodate|dirty|lru|active|slab|owner_priv_1|private|private_2|writeback|head|tail|swapcache|reclaim|swapbacked|unevictable|uncached|compound_lock)
[   59.653604] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor button thermal_sys ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net ata_piix virtio_blk libata virtio_pci virtio_ring virtio scsi_mod
[   59.656998] Pid: 988, comm: bash Not tainted 3.6.0-rc7-guest #12
[   59.657172] Call Trace:
[   59.657275]  [<ffffffff810e9b30>] ? bad_page+0xb0/0x100
[   59.657434]  [<ffffffff810ea4c3>] ? free_pages_prepare+0xb3/0x100
[   59.657610]  [<ffffffff810ea668>] ? free_hot_cold_page+0x48/0x1a0
[   59.657787]  [<ffffffff8112cc08>] ? online_pages_range+0x68/0xa0
[   59.657961]  [<ffffffff8112cba0>] ? __online_page_increment_counters+0x10/0x10
[   59.658162]  [<ffffffff81045561>] ? walk_system_ram_range+0x101/0x110
[   59.658346]  [<ffffffff814c4f95>] ? online_pages+0x1a5/0x2b0
[   59.658515]  [<ffffffff8135663d>] ? __memory_block_change_state+0x20d/0x270
[   59.658710]  [<ffffffff81356756>] ? store_mem_state+0xb6/0xf0
[   59.658878]  [<ffffffff8119e482>] ? sysfs_write_file+0xd2/0x160
[   59.659052]  [<ffffffff8113769a>] ? vfs_write+0xaa/0x160
[   59.659212]  [<ffffffff81137977>] ? sys_write+0x47/0x90
[   59.659371]  [<ffffffff814e2f25>] ? async_page_fault+0x25/0x30
[   59.659543]  [<ffffffff814ea239>] ? system_call_fastpath+0x16/0x1b
[   59.659720] Disabling lock debugging due to kernel taint

Patch 20/21 deals with a similar scenario, but only for __PG_HWPOISON flag.
Did i miss any other patch for this?
Please try the following patch:
From a38ec678e0a9b48b252f457d7910b7527049dc43 Mon Sep 17 00:00:00 2001
From: Wen Congyang <redacted>
Date: Thu, 27 Sep 2012 17:27:57 +0800
Subject: [PATCH] clear the memory to store page information

---
 mm/sparse.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/mm/sparse.c b/mm/sparse.c
index ab9d755..36dda08 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -639,7 +639,6 @@ static struct page *__kmalloc_section_memmap(unsigned long nr_pages)
 got_map_page:
 	ret = (struct page *)pfn_to_kaddr(page_to_pfn(page));
 got_map_ptr:
-	memset(ret, 0, memmap_size);
 
 	return ret;
 }
@@ -761,6 +760,8 @@ int __meminit sparse_add_one_section(struct zone *zone, unsigned long start_pfn,
 		goto out;
 	}
 
+	memset(memmap, 0, sizeof(struct page) * nr_pages);
+
 	ms->section_mem_map |= SECTION_MARKED_PRESENT;
 
 	ret = sparse_init_one_section(ms, section_nr, memmap, usemap);
-- 
1.7.1

Thanks
Wen Congyang

> 
> thanks,
> 
> - Vasilis
> 
> [1] https://lkml.org/lkml/2012/9/6/635
> [2] https://lkml.org/lkml/2012/9/11/542
> [3] https://lkml.org/lkml/2012/9/20/37
> [4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691
> 
> 
> 

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Vasilis Liaskovitis <hidden>
Date: 2012-09-27 10:36:13

On Thu, Sep 27, 2012 at 02:37:14PM +0800, Wen Congyang wrote:
Hi Vasilis Liaskovitis

At 09/27/2012 12:46 AM, Vasilis Liaskovitis Wrote:
quoted
Hi,

I am testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

After succesfull hot-add and online, I am doing a hot-remove with "echo 1 > /sys/bus/acpi/devices/PNP/eject"
When I do the OSPM-eject, I often get slab corruption in "acpi-state" cache, or in other caches
I can't reproduce this problem. Can you provide the following information:
1. config file
2. qemu's command line

You said you did OSPM-eject. Do you mean write 1 to /sys/bus/acpi/devices/PNP0C80:XX/eject?
yes.

example qemu command line with one dimm:

"/opt/qemu-kvm-memhp/bin/qemu-system-x86_64 -bios
/opt/extra/vliaskov/devel/seabios-upstream/out/bios.bin -enable-kvm -M pc -smp
4,maxcpus=8 -cpu host -m 2048 -drive file=/opt/extra/debian-template.raw,if=none,id=drive-virtio-disk0,format=raw
-device virtio-blk-pci,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-vga cirrus -netdev type=tap,id=guest0,vhost=on -device virtio-net-pci,netdev=guest0
-monitor unix:/tmp/qemu.monitor11,server,nowait -chardev stdio,id=seabios  -device
isa-debugcon,iobase=0x402,chardev=seabios
-dimm id=n0,size=512M,node=0"

or last line with 2 numa nodes:
"-dimm id=n0,size=512M,node=0 -dimm id=n1,size=512M,node=1 -numa node,nodeid=0 -numa node,nodeid=1"

attached config. Tree is at:
https://github.com/vliaskov/linux/commits/memhp-fujitsu

thanks,
- Vasilis

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Vasilis Liaskovitis <hidden>
Date: 2012-09-27 11:02:13

On Thu, Sep 27, 2012 at 06:06:30PM +0800, Wen Congyang wrote:
Please try the following patch:
From a38ec678e0a9b48b252f457d7910b7527049dc43 Mon Sep 17 00:00:00 2001
From: Wen Congyang <redacted>
Date: Thu, 27 Sep 2012 17:27:57 +0800
Subject: [PATCH] clear the memory to store page information
this solves the hot re-add problem for me.
thanks for the quick solution.

- Vasilis
quoted hunk
---
 mm/sparse.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/mm/sparse.c b/mm/sparse.c
index ab9d755..36dda08 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -639,7 +639,6 @@ static struct page *__kmalloc_section_memmap(unsigned long nr_pages)
 got_map_page:
 	ret = (struct page *)pfn_to_kaddr(page_to_pfn(page));
 got_map_ptr:
-	memset(ret, 0, memmap_size);
 
 	return ret;
 }
@@ -761,6 +760,8 @@ int __meminit sparse_add_one_section(struct zone *zone, unsigned long start_pfn,
 		goto out;
 	}
 
+	memset(memmap, 0, sizeof(struct page) * nr_pages);
+
 	ms->section_mem_map |= SECTION_MARKED_PRESENT;
 
 	ret = sparse_init_one_section(ms, section_nr, memmap, usemap);
-- 
1.7.1

Thanks
Wen Congyang

> 
> thanks,
> 
> - Vasilis
> 
> [1] https://lkml.org/lkml/2012/9/6/635
> [2] https://lkml.org/lkml/2012/9/11/542
> [3] https://lkml.org/lkml/2012/9/20/37
> [4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691
> 
> 
> 

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Wen Congyang <hidden>
Date: 2012-09-28 02:00:35

At 09/27/2012 06:35 PM, Vasilis Liaskovitis Wrote:
On Thu, Sep 27, 2012 at 02:37:14PM +0800, Wen Congyang wrote:
quoted
Hi Vasilis Liaskovitis

At 09/27/2012 12:46 AM, Vasilis Liaskovitis Wrote:
quoted
Hi,

I am testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

After succesfull hot-add and online, I am doing a hot-remove with "echo 1 > /sys/bus/acpi/devices/PNP/eject"
When I do the OSPM-eject, I often get slab corruption in "acpi-state" cache, or in other caches
I can't reproduce this problem. Can you provide the following information:
1. config file
2. qemu's command line

You said you did OSPM-eject. Do you mean write 1 to /sys/bus/acpi/devices/PNP0C80:XX/eject?
yes.

example qemu command line with one dimm:

"/opt/qemu-kvm-memhp/bin/qemu-system-x86_64 -bios
/opt/extra/vliaskov/devel/seabios-upstream/out/bios.bin -enable-kvm -M pc -smp
4,maxcpus=8 -cpu host -m 2048 -drive file=/opt/extra/debian-template.raw,if=none,id=drive-virtio-disk0,format=raw
-device virtio-blk-pci,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-vga cirrus -netdev type=tap,id=guest0,vhost=on -device virtio-net-pci,netdev=guest0
-monitor unix:/tmp/qemu.monitor11,server,nowait -chardev stdio,id=seabios  -device
isa-debugcon,iobase=0x402,chardev=seabios
-dimm id=n0,size=512M,node=0"

or last line with 2 numa nodes:
"-dimm id=n0,size=512M,node=0 -dimm id=n1,size=512M,node=1 -numa node,nodeid=0 -numa node,nodeid=1"
I have reproduced this problem. It only can be reproduced when the dimm's memory is on node 0.
I investigate it now.

Thanks
Wen Congyang
attached config. Tree is at:
https://github.com/vliaskov/linux/commits/memhp-fujitsu

thanks,
- Vasilis

Re: [RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages()

From: Ni zhan Chen <hidden>
Date: 2012-09-28 02:22:43

On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
From: Yasuaki Ishimatsu <redacted>

remove_memory() only try to offline pages. It is called in two cases:
1. hot remove a memory device
2. echo offline >/sys/devices/system/memory/memoryXX/state

In the 1st case, we should also change memory block's state, and notify
the userspace that the memory block's state is changed after offlining
pages.

So rename remove_memory() to offline_memory()/offline_pages(). And in
the 1st case, offline_memory() will be used. The function offline_memory()
is not implemented. In the 2nd case, offline_pages() will be used.
But this time there is not a function associated with add_memory.
quoted hunk
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
  drivers/acpi/acpi_memhotplug.c |    2 +-
  drivers/base/memory.c          |    9 +++------
  include/linux/memory_hotplug.h |    3 ++-
  mm/memory_hotplug.c            |   22 ++++++++++++++--------
  4 files changed, 20 insertions(+), 16 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 24c807f..2a7beac 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -318,7 +318,7 @@ static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
  	 */
  	list_for_each_entry_safe(info, n, &mem_device->res_list, list) {
  		if (info->enabled) {
-			result = remove_memory(info->start_addr, info->length);
+			result = offline_memory(info->start_addr, info->length);
  			if (result)
  				return result;
  		}
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index 7dda4f7..44e7de6 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -248,26 +248,23 @@ static bool pages_correctly_reserved(unsigned long start_pfn,
  static int
  memory_block_action(unsigned long phys_index, unsigned long action)
  {
-	unsigned long start_pfn, start_paddr;
+	unsigned long start_pfn;
  	unsigned long nr_pages = PAGES_PER_SECTION * sections_per_block;
  	struct page *first_page;
  	int ret;
  
  	first_page = pfn_to_page(phys_index << PFN_SECTION_SHIFT);
+	start_pfn = page_to_pfn(first_page);
  
  	switch (action) {
  		case MEM_ONLINE:
-			start_pfn = page_to_pfn(first_page);
-
  			if (!pages_correctly_reserved(start_pfn, nr_pages))
  				return -EBUSY;
  
  			ret = online_pages(start_pfn, nr_pages);
  			break;
  		case MEM_OFFLINE:
-			start_paddr = page_to_pfn(first_page) << PAGE_SHIFT;
-			ret = remove_memory(start_paddr,
-					    nr_pages << PAGE_SHIFT);
+			ret = offline_pages(start_pfn, nr_pages);
  			break;
  		default:
  			WARN(1, KERN_WARNING "%s(%ld, %ld) unknown action: "
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index 910550f..c183f39 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -233,7 +233,8 @@ static inline int is_mem_section_removable(unsigned long pfn,
  extern int mem_online_node(int nid);
  extern int add_memory(int nid, u64 start, u64 size);
  extern int arch_add_memory(int nid, u64 start, u64 size);
-extern int remove_memory(u64 start, u64 size);
+extern int offline_pages(unsigned long start_pfn, unsigned long nr_pages);
+extern int offline_memory(u64 start, u64 size);
  extern int sparse_add_one_section(struct zone *zone, unsigned long start_pfn,
  								int nr_pages);
  extern void sparse_remove_one_section(struct zone *zone, struct mem_section *ms);
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 3ad25f9..bb42316 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -866,7 +866,7 @@ check_pages_isolated(unsigned long start_pfn, unsigned long end_pfn)
  	return offlined;
  }
  
-static int __ref offline_pages(unsigned long start_pfn,
+static int __ref __offline_pages(unsigned long start_pfn,
  		  unsigned long end_pfn, unsigned long timeout)
  {
  	unsigned long pfn, nr_pages, expire;
@@ -994,18 +994,24 @@ out:
  	return ret;
  }
  
-int remove_memory(u64 start, u64 size)
+int offline_pages(unsigned long start_pfn, unsigned long nr_pages)
  {
-	unsigned long start_pfn, end_pfn;
+	return __offline_pages(start_pfn, start_pfn + nr_pages, 120 * HZ);
+}
  
-	start_pfn = PFN_DOWN(start);
-	end_pfn = start_pfn + PFN_DOWN(size);
-	return offline_pages(start_pfn, end_pfn, 120 * HZ);
+int offline_memory(u64 start, u64 size)
+{
+	return -EINVAL;
  }
  #else
-int remove_memory(u64 start, u64 size)
+int offline_pages(unsigned long start, unsigned long size)
+{
+	return -EINVAL;
+}
+
+int offline_memory(u64 start, u64 size)
  {
  	return -EINVAL;
  }
  #endif /* CONFIG_MEMORY_HOTREMOVE */
-EXPORT_SYMBOL_GPL(remove_memory);
+EXPORT_SYMBOL_GPL(offline_memory);

Re: [RFC v9 PATCH 03/21] memory-hotplug: store the node id in acpi_memory_device

From: Ni zhan Chen <hidden>
Date: 2012-09-28 03:21:54

On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
From: Wen Congyang <redacted>

The memory device has only one node id. Store the node id when
enable the memory device, and we can reuse it when removing the
memory device.
one question:
if use numa emulation, memory device will associated to one node or ...?
quoted hunk
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
Reviewed-by: Yasuaki Ishimatsu <redacted>
---
  drivers/acpi/acpi_memhotplug.c |    4 ++++
  1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 2a7beac..7873832 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -83,6 +83,7 @@ struct acpi_memory_info {
  struct acpi_memory_device {
  	struct acpi_device * device;
  	unsigned int state;	/* State of the memory device */
+	int nid;
  	struct list_head res_list;
  };
  
@@ -256,6 +257,9 @@ static int acpi_memory_enable_device(struct acpi_memory_device *mem_device)
  		info->enabled = 1;
  		num_enabled++;
  	}
+
+	mem_device->nid = node;
+
  	if (!num_enabled) {
  		printk(KERN_ERR PREFIX "add_memory failed\n");
  		mem_device->state = MEMORY_INVALID_STATE;

Re: [RFC v9 PATCH 05/21] memory-hotplug: check whether memory is present or not

From: Ni zhan Chen <hidden>
Date: 2012-09-28 03:37:42

On 09/11/2012 10:24 AM, Yasuaki Ishimatsu wrote:
Hi Wen,

2012/09/11 11:15, Wen Congyang wrote:
quoted
Hi, ishimatsu

At 09/05/2012 05:25 PM, wency@cn.fujitsu.com Wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

If system supports memory hot-remove, online_pages() may online 
removed pages.
So online_pages() need to check whether onlining pages are present 
or not.
Because we use memory_block_change_state() to hotremoving memory, I 
think
this patch can be removed. What do you think?
Pleae teach me detals a little more. If we use 
memory_block_change_state(),
does the conflict never occur? Why?
since memory hot-add or hot-remove is based on memblock, if check in 
memory_block_change_state()
can guarantee conflict never occur?
Thansk,
Yasuaki Ishimatsu
quoted
Thanks
Wen Congyang
quoted
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  include/linux/mmzone.h |   19 +++++++++++++++++++
  mm/memory_hotplug.c    |   13 +++++++++++++
  2 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 2daa54f..ac3ae30 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -1180,6 +1180,25 @@ void sparse_init(void);
  #define sparse_index_init(_sec, _nid)  do {} while (0)
  #endif /* CONFIG_SPARSEMEM */

+#ifdef CONFIG_SPARSEMEM
+static inline int pfns_present(unsigned long pfn, unsigned long 
nr_pages)
+{
+    int i;
+    for (i = 0; i < nr_pages; i++) {
+        if (pfn_present(pfn + i))
+            continue;
+        else
+            return -EINVAL;
+    }
+    return 0;
+}
+#else
+static inline int pfns_present(unsigned long pfn, unsigned long 
nr_pages)
+{
+    return 0;
+}
+#endif /* CONFIG_SPARSEMEM*/
+
  #ifdef CONFIG_NODES_SPAN_OTHER_NODES
  bool early_pfn_in_nid(unsigned long pfn, int nid);
  #else
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 49f7747..299747d 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -467,6 +467,19 @@ int __ref online_pages(unsigned long pfn, 
unsigned long nr_pages)
      struct memory_notify arg;

      lock_memory_hotplug();
+    /*
+     * If system supports memory hot-remove, the memory may have been
+     * removed. So we check whether the memory has been removed or 
not.
+     *
+     * Note: When CONFIG_SPARSEMEM is defined, pfns_present() become
+     *       effective. If CONFIG_SPARSEMEM is not defined, 
pfns_present()
+     *       always returns 0.
+     */
+    ret = pfns_present(pfn, nr_pages);
+    if (ret) {
+        unlock_memory_hotplug();
+        return ret;
+    }
      arg.start_pfn = pfn;
      arg.nr_pages = nr_pages;
      arg.status_change_nid = -1;

-- 
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: [RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages()

From: Yasuaki Ishimatsu <hidden>
Date: 2012-09-28 03:50:43

Hi Chen,

2012/09/28 11:22, Ni zhan Chen wrote:
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

remove_memory() only try to offline pages. It is called in two cases:
1. hot remove a memory device
2. echo offline >/sys/devices/system/memory/memoryXX/state

In the 1st case, we should also change memory block's state, and notify
the userspace that the memory block's state is changed after offlining
pages.

So rename remove_memory() to offline_memory()/offline_pages(). And in
the 1st case, offline_memory() will be used. The function offline_memory()
is not implemented. In the 2nd case, offline_pages() will be used.
But this time there is not a function associated with add_memory.
To associate with add_memory() later, we renamed it.

Thanks,
Yasuaki Ishimatsu
quoted
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
  drivers/acpi/acpi_memhotplug.c |    2 +-
  drivers/base/memory.c          |    9 +++------
  include/linux/memory_hotplug.h |    3 ++-
  mm/memory_hotplug.c            |   22 ++++++++++++++--------
  4 files changed, 20 insertions(+), 16 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 24c807f..2a7beac 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -318,7 +318,7 @@ static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
       */
      list_for_each_entry_safe(info, n, &mem_device->res_list, list) {
          if (info->enabled) {
-            result = remove_memory(info->start_addr, info->length);
+            result = offline_memory(info->start_addr, info->length);
              if (result)
                  return result;
          }
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index 7dda4f7..44e7de6 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -248,26 +248,23 @@ static bool pages_correctly_reserved(unsigned long start_pfn,
  static int
  memory_block_action(unsigned long phys_index, unsigned long action)
  {
-    unsigned long start_pfn, start_paddr;
+    unsigned long start_pfn;
      unsigned long nr_pages = PAGES_PER_SECTION * sections_per_block;
      struct page *first_page;
      int ret;
      first_page = pfn_to_page(phys_index << PFN_SECTION_SHIFT);
+    start_pfn = page_to_pfn(first_page);
      switch (action) {
          case MEM_ONLINE:
-            start_pfn = page_to_pfn(first_page);
-
              if (!pages_correctly_reserved(start_pfn, nr_pages))
                  return -EBUSY;
              ret = online_pages(start_pfn, nr_pages);
              break;
          case MEM_OFFLINE:
-            start_paddr = page_to_pfn(first_page) << PAGE_SHIFT;
-            ret = remove_memory(start_paddr,
-                        nr_pages << PAGE_SHIFT);
+            ret = offline_pages(start_pfn, nr_pages);
              break;
          default:
              WARN(1, KERN_WARNING "%s(%ld, %ld) unknown action: "
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index 910550f..c183f39 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -233,7 +233,8 @@ static inline int is_mem_section_removable(unsigned long pfn,
  extern int mem_online_node(int nid);
  extern int add_memory(int nid, u64 start, u64 size);
  extern int arch_add_memory(int nid, u64 start, u64 size);
-extern int remove_memory(u64 start, u64 size);
+extern int offline_pages(unsigned long start_pfn, unsigned long nr_pages);
+extern int offline_memory(u64 start, u64 size);
  extern int sparse_add_one_section(struct zone *zone, unsigned long start_pfn,
                                  int nr_pages);
  extern void sparse_remove_one_section(struct zone *zone, struct mem_section *ms);
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 3ad25f9..bb42316 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -866,7 +866,7 @@ check_pages_isolated(unsigned long start_pfn, unsigned long end_pfn)
      return offlined;
  }
-static int __ref offline_pages(unsigned long start_pfn,
+static int __ref __offline_pages(unsigned long start_pfn,
            unsigned long end_pfn, unsigned long timeout)
  {
      unsigned long pfn, nr_pages, expire;
@@ -994,18 +994,24 @@ out:
      return ret;
  }
-int remove_memory(u64 start, u64 size)
+int offline_pages(unsigned long start_pfn, unsigned long nr_pages)
  {
-    unsigned long start_pfn, end_pfn;
+    return __offline_pages(start_pfn, start_pfn + nr_pages, 120 * HZ);
+}
-    start_pfn = PFN_DOWN(start);
-    end_pfn = start_pfn + PFN_DOWN(size);
-    return offline_pages(start_pfn, end_pfn, 120 * HZ);
+int offline_memory(u64 start, u64 size)
+{
+    return -EINVAL;
  }
  #else
-int remove_memory(u64 start, u64 size)
+int offline_pages(unsigned long start, unsigned long size)
+{
+    return -EINVAL;
+}
+
+int offline_memory(u64 start, u64 size)
  {
      return -EINVAL;
  }
  #endif /* CONFIG_MEMORY_HOTREMOVE */
-EXPORT_SYMBOL_GPL(remove_memory);
+EXPORT_SYMBOL_GPL(offline_memory);

Re: [RFC v9 PATCH 04/21] memory-hotplug: offline and remove memory when removing the memory device

From: Ni zhan Chen <hidden>
Date: 2012-09-28 04:49:07

On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted hunk
From: Yasuaki Ishimatsu <redacted>

We should offline and remove memory when removing the memory device.
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject

In the 1st case, acpi_memory_disable_device() will be called. In the 2nd
case, acpi_memory_device_remove() will be called. acpi_memory_device_remove()
will also be called when we unbind the memory device from the driver
acpi_memhotplug. If the type is ACPI_BUS_REMOVAL_EJECT, it means
that the user wants to eject the memory device, and we should offline
and remove memory in acpi_memory_device_remove().

The function remove_memory() is not implemeted now. It only check whether
all memory has been offllined now.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
  drivers/acpi/acpi_memhotplug.c |   45 +++++++++++++++++++++++++++++++++------
  drivers/base/memory.c          |   39 ++++++++++++++++++++++++++++++++++
  include/linux/memory.h         |    5 ++++
  include/linux/memory_hotplug.h |    5 ++++
  mm/memory_hotplug.c            |   22 +++++++++++++++++++
  5 files changed, 109 insertions(+), 7 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 7873832..9d47458 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -29,6 +29,7 @@
  #include <linux/module.h>
  #include <linux/init.h>
  #include <linux/types.h>
+#include <linux/memory.h>
  #include <linux/memory_hotplug.h>
  #include <linux/slab.h>
  #include <acpi/acpi_drivers.h>
@@ -310,25 +311,44 @@ static int acpi_memory_powerdown_device(struct acpi_memory_device *mem_device)
  	return 0;
  }
  
-static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
+static int
+acpi_memory_device_remove_memory(struct acpi_memory_device *mem_device)
  {
  	int result;
  	struct acpi_memory_info *info, *n;
+	int node = mem_device->nid;
  
-
-	/*
-	 * Ask the VM to offline this memory range.
-	 * Note: Assume that this function returns zero on success
-	 */
  	list_for_each_entry_safe(info, n, &mem_device->res_list, list) {
  		if (info->enabled) {
  			result = offline_memory(info->start_addr, info->length);
  			if (result)
  				return result;
+
+			result = remove_memory(node, info->start_addr,
+					       info->length);
+			if (result)
+				return result;
  		}
+
+		list_del(&info->list);
  		kfree(info);
  	}
  
+	return 0;
+}
+
+static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
+{
+	int result;
+
+	/*
+	 * Ask the VM to offline this memory range.
+	 * Note: Assume that this function returns zero on success
+	 */
+	result = acpi_memory_device_remove_memory(mem_device);
+	if (result)
+		return result;
+
  	/* Power-off and eject the device */
  	result = acpi_memory_powerdown_device(mem_device);
  	if (result) {
@@ -477,12 +497,23 @@ static int acpi_memory_device_add(struct acpi_device *device)
  static int acpi_memory_device_remove(struct acpi_device *device, int type)
  {
  	struct acpi_memory_device *mem_device = NULL;
-
+	int result;
  
  	if (!device || !acpi_driver_data(device))
  		return -EINVAL;
  
  	mem_device = acpi_driver_data(device);
+
+	if (type == ACPI_BUS_REMOVAL_EJECT) {
+		/*
+		 * offline and remove memory only when the memory device is
+		 * ejected.
+		 */
+		result = acpi_memory_device_remove_memory(mem_device);
+		if (result)
+			return result;
+	}
+
  	kfree(mem_device);
  
  	return 0;
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index 86c8821..038be73 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -70,6 +70,45 @@ void unregister_memory_isolate_notifier(struct notifier_block *nb)
  }
  EXPORT_SYMBOL(unregister_memory_isolate_notifier);
  
+bool is_memblk_offline(unsigned long start, unsigned long size)
+{
+	struct memory_block *mem = NULL;
+	struct mem_section *section;
+	unsigned long start_pfn, end_pfn;
+	unsigned long pfn, section_nr;
+
+	start_pfn = PFN_DOWN(start);
+	end_pfn = PFN_UP(start + size);
+
+	for (pfn = start_pfn; pfn < end_pfn; pfn += PAGES_PER_SECTION) {
+		section_nr = pfn_to_section_nr(pfn);
+		if (!present_section_nr(section_nr))
+			continue;
+
+		section = __nr_to_section(section_nr);
+		/* same memblock? */
+		if (mem)
+			if ((section_nr >= mem->start_section_nr) &&
+			    (section_nr <= mem->end_section_nr))
+				continue;
+
+		mem = find_memory_block_hinted(section, mem);
+		if (!mem)
+			continue;
+		if (mem->state == MEM_OFFLINE)
+			continue;
+
+		kobject_put(&mem->dev.kobj);
+		return false;
+	}
+
+	if (mem)
+		kobject_put(&mem->dev.kobj);
+
+	return true;
+}
+EXPORT_SYMBOL(is_memblk_offline);
+
  /*
   * register_memory - Setup a sysfs device for a memory block
   */
diff --git a/include/linux/memory.h b/include/linux/memory.h
index 1ac7f6e..7c66126 100644
--- a/include/linux/memory.h
+++ b/include/linux/memory.h
@@ -106,6 +106,10 @@ static inline int memory_isolate_notify(unsigned long val, void *v)
  {
  	return 0;
  }
+static inline bool is_memblk_offline(unsigned long start, unsigned long size)
+{
+	return false;
+}
  #else
  extern int register_memory_notifier(struct notifier_block *nb);
  extern void unregister_memory_notifier(struct notifier_block *nb);
@@ -120,6 +124,7 @@ extern int memory_isolate_notify(unsigned long val, void *v);
  extern struct memory_block *find_memory_block_hinted(struct mem_section *,
  							struct memory_block *);
  extern struct memory_block *find_memory_block(struct mem_section *);
+extern bool is_memblk_offline(unsigned long start, unsigned long size);
  #define CONFIG_MEM_BLOCK_SIZE	(PAGES_PER_SECTION<<PAGE_SHIFT)
  enum mem_add_context { BOOT, HOTPLUG };
  #endif /* CONFIG_MEMORY_HOTPLUG_SPARSE */
diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h
index 0b040bb..fd84ea9 100644
--- a/include/linux/memory_hotplug.h
+++ b/include/linux/memory_hotplug.h
@@ -222,6 +222,7 @@ static inline void unlock_memory_hotplug(void) {}
  #ifdef CONFIG_MEMORY_HOTREMOVE
  
  extern int is_mem_section_removable(unsigned long pfn, unsigned long nr_pages);
+extern int remove_memory(int nid, u64 start, u64 size);
  
  #else
  static inline int is_mem_section_removable(unsigned long pfn,
@@ -229,6 +230,10 @@ static inline int is_mem_section_removable(unsigned long pfn,
  {
  	return 0;
  }
+static inline int remove_memory(int nid, u64 start, u64 size)
+{
+	return -EBUSY;
+}
  #endif /* CONFIG_MEMORY_HOTREMOVE */
  
  extern int mem_online_node(int nid);
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 6fc1908..49f7747 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -1038,6 +1038,28 @@ int offline_memory(u64 start, u64 size)
  
  	return 0;
  }
+
+int remove_memory(int nid, u64 start, u64 size)
+{
+	int ret = -EBUSY;
+	lock_memory_hotplug();
+	/*
+	 * The memory might become online by other task, even if you offine it.
s/offine/offline
+	 * So we check whether the memory has been onlined or not.
+	 */
+	if (!is_memblk_offline(start, size)) {
+		pr_warn("memory removing [mem %#010llx-%#010llx] failed, "
+			"because the memmory range is online\n",
+			start, start + size);
+		ret = -EAGAIN;
+	}
+
+	unlock_memory_hotplug();
+	return ret;
+
+}
+EXPORT_SYMBOL_GPL(remove_memory);
+
  #else
  int offline_pages(unsigned long start, unsigned long size)
  {

Re: [RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages()

From: KOSAKI Motohiro <hidden>
Date: 2012-09-28 22:21:45

On Thu, Sep 27, 2012 at 11:50 PM, Yasuaki Ishimatsu
[off-list ref] wrote:
Hi Chen,


2012/09/28 11:22, Ni zhan Chen wrote:
quoted
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

remove_memory() only try to offline pages. It is called in two cases:
1. hot remove a memory device
2. echo offline >/sys/devices/system/memory/memoryXX/state

In the 1st case, we should also change memory block's state, and notify
the userspace that the memory block's state is changed after offlining
pages.

So rename remove_memory() to offline_memory()/offline_pages(). And in
the 1st case, offline_memory() will be used. The function
offline_memory()
is not implemented. In the 2nd case, offline_pages() will be used.

But this time there is not a function associated with add_memory.

To associate with add_memory() later, we renamed it.
Then, you introduced bisect breakage. It is definitely unacceptable.

NAK.

Re: [RFC v9 PATCH 13/21] memory-hotplug: check page type in get_page_bootmem

From: Ni zhan Chen <hidden>
Date: 2012-09-29 02:16:11

On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
From: Yasuaki Ishimatsu <redacted>

The function get_page_bootmem() may be called more than one time to the same
page. There is no need to set page's type, private if the function is not
the first time called to the page.

Note: the patch is just optimization and does not fix any problem.
Hi Yasuaki,

this patch is reasonable to me. I have another question associated to 
get_page_bootmem(), the question is from another fujitsu guy's patch 
changelog [commit : 04753278769f3], the changelog said  that:

  1) When the memmap of removing section is allocated on other
      section by bootmem, it should/can be free.
  2) When the memmap of removing section is allocated on the
      same section, it shouldn't be freed. Because the section has to be
      logical memory offlined already and all pages must be isolated against
      page allocater. If it is freed, page allocator may use it which will
      be removed physically soon.

but I don't see his patch guarantee 2), it means that his patch doesn't 
guarantee the memmap of removing section which is allocated on other 
section by bootmem doesn't be freed. Hopefully get your explaination in 
details, thanks in advance. :-)
quoted hunk
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  mm/memory_hotplug.c |   15 +++++++++++----
  1 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index d736df3..26a5012 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -95,10 +95,17 @@ static void release_memory_resource(struct resource *res)
  static void get_page_bootmem(unsigned long info,  struct page *page,
  			     unsigned long type)
  {
-	page->lru.next = (struct list_head *) type;
-	SetPagePrivate(page);
-	set_page_private(page, info);
-	atomic_inc(&page->_count);
+	unsigned long page_type;
+
+	page_type = (unsigned long)page->lru.next;
+	if (page_type < MEMORY_HOTPLUG_MIN_BOOTMEM_TYPE ||
+	    page_type > MEMORY_HOTPLUG_MAX_BOOTMEM_TYPE){
+		page->lru.next = (struct list_head *)type;
+		SetPagePrivate(page);
+		set_page_private(page, info);
+		atomic_inc(&page->_count);
+	} else
+		atomic_inc(&page->_count);
  }
  
  /* reference to __meminit __free_pages_bootmem is valid

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Ni zhan Chen <hidden>
Date: 2012-09-29 03:45:42

On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
From: Wen Congyang <redacted>

This patch series aims to support physical memory hot-remove.

The patches can free/remove the following things:

   - acpi_memory_info                          : [RFC PATCH 4/19]
   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19]
   - iomem_resource                            : [RFC PATCH 9/19]
   - mem_section and related sysfs files       : [RFC PATCH 10-11, 13-16/19]
   - page table of removed memory              : [RFC PATCH 12/19]
   - node and related sysfs files              : [RFC PATCH 18-19/19]

If you find lack of function for physical memory hot-remove, please let me
know.
Since patchset is too big, could you add more patchset changelog to 
describe how this patchset works? in order that it is easier to review.
How to test this patchset?
1. apply this patchset and build the kernel. MEMORY_HOTPLUG, MEMORY_HOTREMOVE,
    ACPI_HOTPLUG_MEMORY must be selected.
2. load the module acpi_memhotplug
3. hotplug the memory device(it depends on your hardware)
    You will see the memory device under the directory /sys/bus/acpi/devices/.
    Its name is PNP0C80:XX.
4. online/offline pages provided by this memory device
    You can write online/offline to /sys/devices/system/memory/memoryX/state to
    online/offline pages provided by this memory device
5. hotremove the memory device
    You can hotremove the memory device by the hardware, or writing 1 to
    /sys/bus/acpi/devices/PNP0C80:XX/eject.

Note: if the memory provided by the memory device is used by the kernel, it
can't be offlined. It is not a bug.

Known problems:
1. memory can't be offlined when CONFIG_MEMCG is selected.
    For example: there is a memory device on node 1. The address range
    is [1G, 1.5G). You will find 4 new directories memory8, memory9, memory10,
    and memory11 under the directory /sys/devices/system/memory/.
    If CONFIG_MEMCG is selected, we will allocate memory to store page cgroup
    when we online pages. When we online memory8, the memory stored page cgroup
    is not provided by this memory device. But when we online memory9, the memory
    stored page cgroup may be provided by memory8. So we can't offline memory8
    now. We should offline the memory in the reversed order.
    When the memory device is hotremoved, we will auto offline memory provided
    by this memory device. But we don't know which memory is onlined first, so
    offlining memory may fail. In such case, you should offline the memory by
    hand before hotremoving the memory device.
2. hotremoving memory device may cause kernel panicked
    This bug will be fixed by Liu Jiang's patch:
    https://lkml.org/lkml/2012/7/3/1

change log of v9:
  [RFC PATCH v9 8/21]
    * add a lock to protect the list map_entries
    * add an indicator to firmware_map_entry to remember whether the memory
      is allocated from bootmem
  [RFC PATCH v9 10/21]
    * change the macro to inline function
  [RFC PATCH v9 19/21]
    * don't offline the node if the cpu on the node is onlined
  [RFC PATCH v9 21/21]
    * create new patch: auto offline page_cgroup when onlining memory block
      failed

change log of v8:
  [RFC PATCH v8 17/20]
    * Fix problems when one node's range include the other nodes
  [RFC PATCH v8 18/20]
    * fix building error when CONFIG_MEMORY_HOTPLUG_SPARSE or CONFIG_HUGETLBFS
      is not defined.
  [RFC PATCH v8 19/20]
    * don't offline node when some memory sections are not removed
  [RFC PATCH v8 20/20]
    * create new patch: clear hwpoisoned flag when onlining pages

change log of v7:
  [RFC PATCH v7 4/19]
    * do not continue if acpi_memory_device_remove_memory() fails.
  [RFC PATCH v7 15/19]
    * handle usemap in register_page_bootmem_info_section() too.

change log of v6:
  [RFC PATCH v6 12/19]
    * fix building error on other archtitectures than x86

  [RFC PATCH v6 15-16/19]
    * fix building error on other archtitectures than x86

change log of v5:
  * merge the patchset to clear page table and the patchset to hot remove
    memory(from ishimatsu) to one big patchset.

  [RFC PATCH v5 1/19]
    * rename remove_memory() to offline_memory()/offline_pages()

  [RFC PATCH v5 2/19]
    * new patch: implement offline_memory(). This function offlines pages,
      update memory block's state, and notify the userspace that the memory
      block's state is changed.

  [RFC PATCH v5 4/19]
    * offline and remove memory in acpi_memory_disable_device() too.

  [RFC PATCH v5 17/19]
    * new patch: add a new function __remove_zone() to revert the things done
      in the function __add_zone().

  [RFC PATCH v5 18/19]
    * flush work befor reseting node device.

change log of v4:
  * remove "memory-hotplug : unify argument of firmware_map_add_early/hotplug"
    from the patch series, since the patch is a bugfix. It is being disccussed
    on other thread. But for testing the patch series, the patch is needed.
    So I added the patch as [PATCH 0/13].

  [RFC PATCH v4 2/13]
    * check memory is online or not at remove_memory()
    * add memory_add_physaddr_to_nid() to acpi_memory_device_remove() for
      getting node id
  
  [RFC PATCH v4 3/13]
    * create new patch : check memory is online or not at online_pages()

  [RFC PATCH v4 4/13]
    * add __ref section to remove_memory()
    * call firmware_map_remove_entry() before remove_sysfs_fw_map_entry()

  [RFC PATCH v4 11/13]
    * rewrite register_page_bootmem_memmap() for removing page used as PT/PMD

change log of v3:
  * rebase to 3.5.0-rc6

  [RFC PATCH v2 2/13]
    * remove extra kobject_put()

    * The patch was commented by Wen. Wen's comment is
      "acpi_memory_device_remove() should ignore a return value of
      remove_memory() since caller does not care the return value".
      But I did not change it since I think caller should care the
      return value. And I am trying to fix it as follow:

      https://lkml.org/lkml/2012/7/5/624

  [RFC PATCH v2 4/13]
    * remove a firmware_memmap_entry allocated by kzmalloc()

change log of v2:
  [RFC PATCH v2 2/13]
    * check whether memory block is offline or not before calling offline_memory()
    * check whether section is valid or not in is_memblk_offline()
    * call kobject_put() for each memory_block in is_memblk_offline()

  [RFC PATCH v2 3/13]
    * unify the end argument of firmware_map_add_early/hotplug

  [RFC PATCH v2 4/13]
    * add release_firmware_map_entry() for freeing firmware_map_entry

  [RFC PATCH v2 6/13]
   * add release_memory_block() for freeing memory_block

  [RFC PATCH v2 11/13]
   * fix wrong arguments of free_pages()


Wen Congyang (8):
   memory-hotplug: implement offline_memory()
   memory-hotplug: store the node id in acpi_memory_device
   memory-hotplug: export the function acpi_bus_remove()
   memory-hotplug: call acpi_bus_remove() to remove memory device
   memory-hotplug: introduce new function arch_remove_memory()
   memory-hotplug: remove sysfs file of node
   memory-hotplug: clear hwpoisoned flag when onlining pages
   memory-hotplug: auto offline page_cgroup when onlining memory block
     failed

Yasuaki Ishimatsu (13):
   memory-hotplug: rename remove_memory() to
     offline_memory()/offline_pages()
   memory-hotplug: offline and remove memory when removing the memory
     device
   memory-hotplug: check whether memory is present or not
   memory-hotplug: remove /sys/firmware/memmap/X sysfs
   memory-hotplug: does not release memory region in PAGES_PER_SECTION
     chunks
   memory-hotplug: add memory_block_release
   memory-hotplug: remove_memory calls __remove_pages
   memory-hotplug: check page type in get_page_bootmem
   memory-hotplug: move register_page_bootmem_info_node and
     put_page_bootmem for sparse-vmemmap
   memory-hotplug: implement register_page_bootmem_info_section of
     sparse-vmemmap
   memory-hotplug: free memmap of sparse-vmemmap
   memory_hotplug: clear zone when the memory is removed
   memory-hotplug: add node_device_release

  arch/ia64/mm/discontig.c                        |   14 +
  arch/ia64/mm/init.c                             |   16 +
  arch/powerpc/mm/init_64.c                       |   14 +
  arch/powerpc/mm/mem.c                           |   14 +
  arch/powerpc/platforms/pseries/hotplug-memory.c |   16 +-
  arch/s390/mm/init.c                             |   12 +
  arch/s390/mm/vmem.c                             |   14 +
  arch/sh/mm/init.c                               |   15 +
  arch/sparc/mm/init_64.c                         |   14 +
  arch/tile/mm/init.c                             |    8 +
  arch/x86/include/asm/pgtable_types.h            |    1 +
  arch/x86/mm/init_32.c                           |   10 +
  arch/x86/mm/init_64.c                           |  331 ++++++++++++++++++
  arch/x86/mm/pageattr.c                          |   47 ++--
  drivers/acpi/acpi_memhotplug.c                  |   54 +++-
  drivers/acpi/scan.c                             |    3 +-
  drivers/base/memory.c                           |   88 ++++-
  drivers/base/node.c                             |   11 +
  drivers/firmware/memmap.c                       |   98 +++++-
  include/acpi/acpi_bus.h                         |    1 +
  include/linux/firmware-map.h                    |    6 +
  include/linux/memory.h                          |    5 +
  include/linux/memory_hotplug.h                  |   25 +-
  include/linux/mm.h                              |    5 +-
  include/linux/mmzone.h                          |   19 +
  mm/memory_hotplug.c                             |  424 +++++++++++++++++++++--
  mm/page_cgroup.c                                |    3 +
  mm/sparse.c                                     |    5 +-
  28 files changed, 1181 insertions(+), 92 deletions(-)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Ni zhan Chen <hidden>
Date: 2012-09-29 08:19:59

On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
From: Wen Congyang <redacted>

This patch series aims to support physical memory hot-remove.

The patches can free/remove the following things:

   - acpi_memory_info                          : [RFC PATCH 4/19]
   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19]
   - iomem_resource                            : [RFC PATCH 9/19]
   - mem_section and related sysfs files       : [RFC PATCH 10-11, 13-16/19]
   - page table of removed memory              : [RFC PATCH 12/19]
   - node and related sysfs files              : [RFC PATCH 18-19/19]

If you find lack of function for physical memory hot-remove, please let me
know.

How to test this patchset?
1. apply this patchset and build the kernel. MEMORY_HOTPLUG, MEMORY_HOTREMOVE,
    ACPI_HOTPLUG_MEMORY must be selected.
2. load the module acpi_memhotplug
Hi Yasuaki,

where is the acpi_memhotplug module?
3. hotplug the memory device(it depends on your hardware)
    You will see the memory device under the directory /sys/bus/acpi/devices/.
    Its name is PNP0C80:XX.
4. online/offline pages provided by this memory device
    You can write online/offline to /sys/devices/system/memory/memoryX/state to
    online/offline pages provided by this memory device
5. hotremove the memory device
    You can hotremove the memory device by the hardware, or writing 1 to
    /sys/bus/acpi/devices/PNP0C80:XX/eject.

Note: if the memory provided by the memory device is used by the kernel, it
can't be offlined. It is not a bug.

Known problems:
1. memory can't be offlined when CONFIG_MEMCG is selected.
    For example: there is a memory device on node 1. The address range
    is [1G, 1.5G). You will find 4 new directories memory8, memory9, memory10,
    and memory11 under the directory /sys/devices/system/memory/.
    If CONFIG_MEMCG is selected, we will allocate memory to store page cgroup
    when we online pages. When we online memory8, the memory stored page cgroup
    is not provided by this memory device. But when we online memory9, the memory
    stored page cgroup may be provided by memory8. So we can't offline memory8
    now. We should offline the memory in the reversed order.
    When the memory device is hotremoved, we will auto offline memory provided
    by this memory device. But we don't know which memory is onlined first, so
    offlining memory may fail. In such case, you should offline the memory by
    hand before hotremoving the memory device.
2. hotremoving memory device may cause kernel panicked
    This bug will be fixed by Liu Jiang's patch:
    https://lkml.org/lkml/2012/7/3/1

change log of v9:
  [RFC PATCH v9 8/21]
    * add a lock to protect the list map_entries
    * add an indicator to firmware_map_entry to remember whether the memory
      is allocated from bootmem
  [RFC PATCH v9 10/21]
    * change the macro to inline function
  [RFC PATCH v9 19/21]
    * don't offline the node if the cpu on the node is onlined
  [RFC PATCH v9 21/21]
    * create new patch: auto offline page_cgroup when onlining memory block
      failed

change log of v8:
  [RFC PATCH v8 17/20]
    * Fix problems when one node's range include the other nodes
  [RFC PATCH v8 18/20]
    * fix building error when CONFIG_MEMORY_HOTPLUG_SPARSE or CONFIG_HUGETLBFS
      is not defined.
  [RFC PATCH v8 19/20]
    * don't offline node when some memory sections are not removed
  [RFC PATCH v8 20/20]
    * create new patch: clear hwpoisoned flag when onlining pages

change log of v7:
  [RFC PATCH v7 4/19]
    * do not continue if acpi_memory_device_remove_memory() fails.
  [RFC PATCH v7 15/19]
    * handle usemap in register_page_bootmem_info_section() too.

change log of v6:
  [RFC PATCH v6 12/19]
    * fix building error on other archtitectures than x86

  [RFC PATCH v6 15-16/19]
    * fix building error on other archtitectures than x86

change log of v5:
  * merge the patchset to clear page table and the patchset to hot remove
    memory(from ishimatsu) to one big patchset.

  [RFC PATCH v5 1/19]
    * rename remove_memory() to offline_memory()/offline_pages()

  [RFC PATCH v5 2/19]
    * new patch: implement offline_memory(). This function offlines pages,
      update memory block's state, and notify the userspace that the memory
      block's state is changed.

  [RFC PATCH v5 4/19]
    * offline and remove memory in acpi_memory_disable_device() too.

  [RFC PATCH v5 17/19]
    * new patch: add a new function __remove_zone() to revert the things done
      in the function __add_zone().

  [RFC PATCH v5 18/19]
    * flush work befor reseting node device.

change log of v4:
  * remove "memory-hotplug : unify argument of firmware_map_add_early/hotplug"
    from the patch series, since the patch is a bugfix. It is being disccussed
    on other thread. But for testing the patch series, the patch is needed.
    So I added the patch as [PATCH 0/13].

  [RFC PATCH v4 2/13]
    * check memory is online or not at remove_memory()
    * add memory_add_physaddr_to_nid() to acpi_memory_device_remove() for
      getting node id
  
  [RFC PATCH v4 3/13]
    * create new patch : check memory is online or not at online_pages()

  [RFC PATCH v4 4/13]
    * add __ref section to remove_memory()
    * call firmware_map_remove_entry() before remove_sysfs_fw_map_entry()

  [RFC PATCH v4 11/13]
    * rewrite register_page_bootmem_memmap() for removing page used as PT/PMD

change log of v3:
  * rebase to 3.5.0-rc6

  [RFC PATCH v2 2/13]
    * remove extra kobject_put()

    * The patch was commented by Wen. Wen's comment is
      "acpi_memory_device_remove() should ignore a return value of
      remove_memory() since caller does not care the return value".
      But I did not change it since I think caller should care the
      return value. And I am trying to fix it as follow:

      https://lkml.org/lkml/2012/7/5/624

  [RFC PATCH v2 4/13]
    * remove a firmware_memmap_entry allocated by kzmalloc()

change log of v2:
  [RFC PATCH v2 2/13]
    * check whether memory block is offline or not before calling offline_memory()
    * check whether section is valid or not in is_memblk_offline()
    * call kobject_put() for each memory_block in is_memblk_offline()

  [RFC PATCH v2 3/13]
    * unify the end argument of firmware_map_add_early/hotplug

  [RFC PATCH v2 4/13]
    * add release_firmware_map_entry() for freeing firmware_map_entry

  [RFC PATCH v2 6/13]
   * add release_memory_block() for freeing memory_block

  [RFC PATCH v2 11/13]
   * fix wrong arguments of free_pages()


Wen Congyang (8):
   memory-hotplug: implement offline_memory()
   memory-hotplug: store the node id in acpi_memory_device
   memory-hotplug: export the function acpi_bus_remove()
   memory-hotplug: call acpi_bus_remove() to remove memory device
   memory-hotplug: introduce new function arch_remove_memory()
   memory-hotplug: remove sysfs file of node
   memory-hotplug: clear hwpoisoned flag when onlining pages
   memory-hotplug: auto offline page_cgroup when onlining memory block
     failed

Yasuaki Ishimatsu (13):
   memory-hotplug: rename remove_memory() to
     offline_memory()/offline_pages()
   memory-hotplug: offline and remove memory when removing the memory
     device
   memory-hotplug: check whether memory is present or not
   memory-hotplug: remove /sys/firmware/memmap/X sysfs
   memory-hotplug: does not release memory region in PAGES_PER_SECTION
     chunks
   memory-hotplug: add memory_block_release
   memory-hotplug: remove_memory calls __remove_pages
   memory-hotplug: check page type in get_page_bootmem
   memory-hotplug: move register_page_bootmem_info_node and
     put_page_bootmem for sparse-vmemmap
   memory-hotplug: implement register_page_bootmem_info_section of
     sparse-vmemmap
   memory-hotplug: free memmap of sparse-vmemmap
   memory_hotplug: clear zone when the memory is removed
   memory-hotplug: add node_device_release

  arch/ia64/mm/discontig.c                        |   14 +
  arch/ia64/mm/init.c                             |   16 +
  arch/powerpc/mm/init_64.c                       |   14 +
  arch/powerpc/mm/mem.c                           |   14 +
  arch/powerpc/platforms/pseries/hotplug-memory.c |   16 +-
  arch/s390/mm/init.c                             |   12 +
  arch/s390/mm/vmem.c                             |   14 +
  arch/sh/mm/init.c                               |   15 +
  arch/sparc/mm/init_64.c                         |   14 +
  arch/tile/mm/init.c                             |    8 +
  arch/x86/include/asm/pgtable_types.h            |    1 +
  arch/x86/mm/init_32.c                           |   10 +
  arch/x86/mm/init_64.c                           |  331 ++++++++++++++++++
  arch/x86/mm/pageattr.c                          |   47 ++--
  drivers/acpi/acpi_memhotplug.c                  |   54 +++-
  drivers/acpi/scan.c                             |    3 +-
  drivers/base/memory.c                           |   88 ++++-
  drivers/base/node.c                             |   11 +
  drivers/firmware/memmap.c                       |   98 +++++-
  include/acpi/acpi_bus.h                         |    1 +
  include/linux/firmware-map.h                    |    6 +
  include/linux/memory.h                          |    5 +
  include/linux/memory_hotplug.h                  |   25 +-
  include/linux/mm.h                              |    5 +-
  include/linux/mmzone.h                          |   19 +
  mm/memory_hotplug.c                             |  424 +++++++++++++++++++++--
  mm/page_cgroup.c                                |    3 +
  mm/sparse.c                                     |    5 +-
  28 files changed, 1181 insertions(+), 92 deletions(-)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: [RFC v9 PATCH 13/21] memory-hotplug: check page type in get_page_bootmem

From: Yasuaki Ishimatsu <hidden>
Date: 2012-10-01 03:03:56

Hi Chen,

2012/09/29 11:15, Ni zhan Chen wrote:
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

The function get_page_bootmem() may be called more than one time to the same
page. There is no need to set page's type, private if the function is not
the first time called to the page.

Note: the patch is just optimization and does not fix any problem.
Hi Yasuaki,

this patch is reasonable to me. I have another question associated to get_page_bootmem(), the question is from another fujitsu guy's patch changelog [commit : 04753278769f3], the changelog said  that:

  1) When the memmap of removing section is allocated on other
      section by bootmem, it should/can be free.
  2) When the memmap of removing section is allocated on the
      same section, it shouldn't be freed. Because the section has to be
      logical memory offlined already and all pages must be isolated against
      page allocater. If it is freed, page allocator may use it which will
      be removed physically soon.

but I don't see his patch guarantee 2), it means that his patch doesn't guarantee the memmap of removing section which is allocated on other section by bootmem doesn't be freed. Hopefully get your explaination in details, thanks in advance. :-)
In my understanding, the patch does not guarantee it.
Please see [commit : 0c0a4a517a31e]. free_map_bootmem() in the commit
guarantees it.

Thanks,
Yasuaki Ishimatsu
quoted
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  mm/memory_hotplug.c |   15 +++++++++++----
  1 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index d736df3..26a5012 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -95,10 +95,17 @@ static void release_memory_resource(struct resource *res)
  static void get_page_bootmem(unsigned long info,  struct page *page,
                   unsigned long type)
  {
-    page->lru.next = (struct list_head *) type;
-    SetPagePrivate(page);
-    set_page_private(page, info);
-    atomic_inc(&page->_count);
+    unsigned long page_type;
+
+    page_type = (unsigned long)page->lru.next;
+    if (page_type < MEMORY_HOTPLUG_MIN_BOOTMEM_TYPE ||
+        page_type > MEMORY_HOTPLUG_MAX_BOOTMEM_TYPE){
+        page->lru.next = (struct list_head *)type;
+        SetPagePrivate(page);
+        set_page_private(page, info);
+        atomic_inc(&page->_count);
+    } else
+        atomic_inc(&page->_count);
  }
  /* reference to __meminit __free_pages_bootmem is valid

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Yasuaki Ishimatsu <hidden>
Date: 2012-10-01 04:45:24

Hi Chen,

2012/09/29 17:19, Ni zhan Chen wrote:
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Wen Congyang <redacted>

This patch series aims to support physical memory hot-remove.

The patches can free/remove the following things:

   - acpi_memory_info                          : [RFC PATCH 4/19]
   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19]
   - iomem_resource                            : [RFC PATCH 9/19]
   - mem_section and related sysfs files       : [RFC PATCH 10-11, 13-16/19]
   - page table of removed memory              : [RFC PATCH 12/19]
   - node and related sysfs files              : [RFC PATCH 18-19/19]

If you find lack of function for physical memory hot-remove, please let me
know.

How to test this patchset?
1. apply this patchset and build the kernel. MEMORY_HOTPLUG, MEMORY_HOTREMOVE,
    ACPI_HOTPLUG_MEMORY must be selected.
2. load the module acpi_memhotplug
Hi Yasuaki,

where is the acpi_memhotplug module?
If you build acpi_memhotplug as module, it is created under
/lib/modules/<kernel-version>/driver/acpi/ directory. It depends
on config ACPI_HOTPLUG_MEMORY. The confing is [*], it becomes built-in
function. So you don't need to care about it.  

Thanks,
Yasuaki Ishimatsu
quoted
3. hotplug the memory device(it depends on your hardware)
    You will see the memory device under the directory /sys/bus/acpi/devices/.
    Its name is PNP0C80:XX.
4. online/offline pages provided by this memory device
    You can write online/offline to /sys/devices/system/memory/memoryX/state to
    online/offline pages provided by this memory device
5. hotremove the memory device
    You can hotremove the memory device by the hardware, or writing 1 to
    /sys/bus/acpi/devices/PNP0C80:XX/eject.

Note: if the memory provided by the memory device is used by the kernel, it
can't be offlined. It is not a bug.

Known problems:
1. memory can't be offlined when CONFIG_MEMCG is selected.
    For example: there is a memory device on node 1. The address range
    is [1G, 1.5G). You will find 4 new directories memory8, memory9, memory10,
    and memory11 under the directory /sys/devices/system/memory/.
    If CONFIG_MEMCG is selected, we will allocate memory to store page cgroup
    when we online pages. When we online memory8, the memory stored page cgroup
    is not provided by this memory device. But when we online memory9, the memory
    stored page cgroup may be provided by memory8. So we can't offline memory8
    now. We should offline the memory in the reversed order.
    When the memory device is hotremoved, we will auto offline memory provided
    by this memory device. But we don't know which memory is onlined first, so
    offlining memory may fail. In such case, you should offline the memory by
    hand before hotremoving the memory device.
2. hotremoving memory device may cause kernel panicked
    This bug will be fixed by Liu Jiang's patch:
    https://lkml.org/lkml/2012/7/3/1

change log of v9:
  [RFC PATCH v9 8/21]
    * add a lock to protect the list map_entries
    * add an indicator to firmware_map_entry to remember whether the memory
      is allocated from bootmem
  [RFC PATCH v9 10/21]
    * change the macro to inline function
  [RFC PATCH v9 19/21]
    * don't offline the node if the cpu on the node is onlined
  [RFC PATCH v9 21/21]
    * create new patch: auto offline page_cgroup when onlining memory block
      failed

change log of v8:
  [RFC PATCH v8 17/20]
    * Fix problems when one node's range include the other nodes
  [RFC PATCH v8 18/20]
    * fix building error when CONFIG_MEMORY_HOTPLUG_SPARSE or CONFIG_HUGETLBFS
      is not defined.
  [RFC PATCH v8 19/20]
    * don't offline node when some memory sections are not removed
  [RFC PATCH v8 20/20]
    * create new patch: clear hwpoisoned flag when onlining pages

change log of v7:
  [RFC PATCH v7 4/19]
    * do not continue if acpi_memory_device_remove_memory() fails.
  [RFC PATCH v7 15/19]
    * handle usemap in register_page_bootmem_info_section() too.

change log of v6:
  [RFC PATCH v6 12/19]
    * fix building error on other archtitectures than x86

  [RFC PATCH v6 15-16/19]
    * fix building error on other archtitectures than x86

change log of v5:
  * merge the patchset to clear page table and the patchset to hot remove
    memory(from ishimatsu) to one big patchset.

  [RFC PATCH v5 1/19]
    * rename remove_memory() to offline_memory()/offline_pages()

  [RFC PATCH v5 2/19]
    * new patch: implement offline_memory(). This function offlines pages,
      update memory block's state, and notify the userspace that the memory
      block's state is changed.

  [RFC PATCH v5 4/19]
    * offline and remove memory in acpi_memory_disable_device() too.

  [RFC PATCH v5 17/19]
    * new patch: add a new function __remove_zone() to revert the things done
      in the function __add_zone().

  [RFC PATCH v5 18/19]
    * flush work befor reseting node device.

change log of v4:
  * remove "memory-hotplug : unify argument of firmware_map_add_early/hotplug"
    from the patch series, since the patch is a bugfix. It is being disccussed
    on other thread. But for testing the patch series, the patch is needed.
    So I added the patch as [PATCH 0/13].

  [RFC PATCH v4 2/13]
    * check memory is online or not at remove_memory()
    * add memory_add_physaddr_to_nid() to acpi_memory_device_remove() for
      getting node id
  [RFC PATCH v4 3/13]
    * create new patch : check memory is online or not at online_pages()

  [RFC PATCH v4 4/13]
    * add __ref section to remove_memory()
    * call firmware_map_remove_entry() before remove_sysfs_fw_map_entry()

  [RFC PATCH v4 11/13]
    * rewrite register_page_bootmem_memmap() for removing page used as PT/PMD

change log of v3:
  * rebase to 3.5.0-rc6

  [RFC PATCH v2 2/13]
    * remove extra kobject_put()

    * The patch was commented by Wen. Wen's comment is
      "acpi_memory_device_remove() should ignore a return value of
      remove_memory() since caller does not care the return value".
      But I did not change it since I think caller should care the
      return value. And I am trying to fix it as follow:

      https://lkml.org/lkml/2012/7/5/624

  [RFC PATCH v2 4/13]
    * remove a firmware_memmap_entry allocated by kzmalloc()

change log of v2:
  [RFC PATCH v2 2/13]
    * check whether memory block is offline or not before calling offline_memory()
    * check whether section is valid or not in is_memblk_offline()
    * call kobject_put() for each memory_block in is_memblk_offline()

  [RFC PATCH v2 3/13]
    * unify the end argument of firmware_map_add_early/hotplug

  [RFC PATCH v2 4/13]
    * add release_firmware_map_entry() for freeing firmware_map_entry

  [RFC PATCH v2 6/13]
   * add release_memory_block() for freeing memory_block

  [RFC PATCH v2 11/13]
   * fix wrong arguments of free_pages()


Wen Congyang (8):
   memory-hotplug: implement offline_memory()
   memory-hotplug: store the node id in acpi_memory_device
   memory-hotplug: export the function acpi_bus_remove()
   memory-hotplug: call acpi_bus_remove() to remove memory device
   memory-hotplug: introduce new function arch_remove_memory()
   memory-hotplug: remove sysfs file of node
   memory-hotplug: clear hwpoisoned flag when onlining pages
   memory-hotplug: auto offline page_cgroup when onlining memory block
     failed

Yasuaki Ishimatsu (13):
   memory-hotplug: rename remove_memory() to
     offline_memory()/offline_pages()
   memory-hotplug: offline and remove memory when removing the memory
     device
   memory-hotplug: check whether memory is present or not
   memory-hotplug: remove /sys/firmware/memmap/X sysfs
   memory-hotplug: does not release memory region in PAGES_PER_SECTION
     chunks
   memory-hotplug: add memory_block_release
   memory-hotplug: remove_memory calls __remove_pages
   memory-hotplug: check page type in get_page_bootmem
   memory-hotplug: move register_page_bootmem_info_node and
     put_page_bootmem for sparse-vmemmap
   memory-hotplug: implement register_page_bootmem_info_section of
     sparse-vmemmap
   memory-hotplug: free memmap of sparse-vmemmap
   memory_hotplug: clear zone when the memory is removed
   memory-hotplug: add node_device_release

  arch/ia64/mm/discontig.c                        |   14 +
  arch/ia64/mm/init.c                             |   16 +
  arch/powerpc/mm/init_64.c                       |   14 +
  arch/powerpc/mm/mem.c                           |   14 +
  arch/powerpc/platforms/pseries/hotplug-memory.c |   16 +-
  arch/s390/mm/init.c                             |   12 +
  arch/s390/mm/vmem.c                             |   14 +
  arch/sh/mm/init.c                               |   15 +
  arch/sparc/mm/init_64.c                         |   14 +
  arch/tile/mm/init.c                             |    8 +
  arch/x86/include/asm/pgtable_types.h            |    1 +
  arch/x86/mm/init_32.c                           |   10 +
  arch/x86/mm/init_64.c                           |  331 ++++++++++++++++++
  arch/x86/mm/pageattr.c                          |   47 ++--
  drivers/acpi/acpi_memhotplug.c                  |   54 +++-
  drivers/acpi/scan.c                             |    3 +-
  drivers/base/memory.c                           |   88 ++++-
  drivers/base/node.c                             |   11 +
  drivers/firmware/memmap.c                       |   98 +++++-
  include/acpi/acpi_bus.h                         |    1 +
  include/linux/firmware-map.h                    |    6 +
  include/linux/memory.h                          |    5 +
  include/linux/memory_hotplug.h                  |   25 +-
  include/linux/mm.h                              |    5 +-
  include/linux/mmzone.h                          |   19 +
  mm/memory_hotplug.c                             |  424 +++++++++++++++++++++--
  mm/page_cgroup.c                                |    3 +
  mm/sparse.c                                     |    5 +-
  28 files changed, 1181 insertions(+), 92 deletions(-)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: [RFC v9 PATCH 03/21] memory-hotplug: store the node id in acpi_memory_device

From: Yasuaki Ishimatsu <hidden>
Date: 2012-10-01 07:39:27

Hi Chen,

2012/09/28 12:21, Ni zhan Chen wrote:
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Wen Congyang <redacted>

The memory device has only one node id. Store the node id when
enable the memory device, and we can reuse it when removing the
memory device.
one question:
if use numa emulation, memory device will associated to one node or ...?
Memory device has only one node, even if you use numa emulation.

Thanks,
Yasuaki Ishimatsu
quoted
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
Reviewed-by: Yasuaki Ishimatsu <redacted>
---
  drivers/acpi/acpi_memhotplug.c |    4 ++++
  1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 2a7beac..7873832 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -83,6 +83,7 @@ struct acpi_memory_info {
  struct acpi_memory_device {
      struct acpi_device * device;
      unsigned int state;    /* State of the memory device */
+    int nid;
      struct list_head res_list;
  };
@@ -256,6 +257,9 @@ static int acpi_memory_enable_device(struct acpi_memory_device *mem_device)
          info->enabled = 1;
          num_enabled++;
      }
+
+    mem_device->nid = node;
+
      if (!num_enabled) {
          printk(KERN_ERR PREFIX "add_memory failed\n");
          mem_device->state = MEMORY_INVALID_STATE;

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Ni zhan Chen <hidden>
Date: 2012-10-01 23:46:13

On 10/01/2012 12:44 PM, Yasuaki Ishimatsu wrote:
Hi Chen,

2012/09/29 17:19, Ni zhan Chen wrote:
quoted
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Wen Congyang <redacted>

This patch series aims to support physical memory hot-remove.

The patches can free/remove the following things:

   - acpi_memory_info                          : [RFC PATCH 4/19]
   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19]
   - iomem_resource                            : [RFC PATCH 9/19]
   - mem_section and related sysfs files       : [RFC PATCH 10-11, 
13-16/19]
   - page table of removed memory              : [RFC PATCH 12/19]
   - node and related sysfs files              : [RFC PATCH 18-19/19]

If you find lack of function for physical memory hot-remove, please 
let me
know.

How to test this patchset?
1. apply this patchset and build the kernel. MEMORY_HOTPLUG, 
MEMORY_HOTREMOVE,
    ACPI_HOTPLUG_MEMORY must be selected.
2. load the module acpi_memhotplug
Hi Yasuaki,

where is the acpi_memhotplug module?
If you build acpi_memhotplug as module, it is created under
/lib/modules/<kernel-version>/driver/acpi/ directory. It depends
on config ACPI_HOTPLUG_MEMORY. The confing is [*], it becomes built-in
function. So you don't need to care about it.
Thanks,
Yasuaki Ishimatsu
Hi Yasuaki,

I build the kernel, MEMORY_HOTPLUG, MEMORY_HOTREMOVE, 
ACPI_HOTPLUG_MEMORY are seleted as [*], but I can't find PNP0C80:XX 
under the directory /sys/bus/acpi/devices/.

[root@localhost ~]# ls /sys/bus/acpi/devices/
device:00  device:07  device:0e  device:15  device:1c  device:23 
device:2a   LNXCPU:00  LNXCPU:07    PNP0501:00  PNP0C02:00 PNP0C0F:02  
PNP0C14:01
device:01  device:08  device:0f  device:16  device:1d  device:24 
device:2b   LNXCPU:01  LNXPWRBN:00  PNP0800:00  PNP0C02:01 PNP0C0F:03  
PNP0C31:00
device:02  device:09  device:10  device:17  device:1e  device:25 
device:2c   LNXCPU:02  LNXSYSTM:00  PNP0A08:00  PNP0C02:02 PNP0C0F:04
device:03  device:0a  device:11  device:18  device:1f  device:26 
device:2d   LNXCPU:03  PNP0000:00   PNP0B00:00  PNP0C04:00 PNP0C0F:05
device:04  device:0b  device:12  device:19  device:20  device:27 
device:2e   LNXCPU:04  PNP0100:00   PNP0C01:00  PNP0C0C:00 PNP0C0F:06
device:05  device:0c  device:13  device:1a  device:21  device:28 
device:2f   LNXCPU:05  PNP0103:00   PNP0C01:01  PNP0C0F:00 PNP0C0F:07
device:06  device:0d  device:14  device:1b  device:22  device:29 
INT3F0D:00  LNXCPU:06  PNP0200:00   PNP0C01:02  PNP0C0F:01 PNP0C14:00

then what I miss ? thanks.
quoted
quoted
3. hotplug the memory device(it depends on your hardware)
    You will see the memory device under the directory 
/sys/bus/acpi/devices/.
    Its name is PNP0C80:XX.
4. online/offline pages provided by this memory device
    You can write online/offline to 
/sys/devices/system/memory/memoryX/state to
    online/offline pages provided by this memory device
5. hotremove the memory device
    You can hotremove the memory device by the hardware, or writing 
1 to
    /sys/bus/acpi/devices/PNP0C80:XX/eject.

Note: if the memory provided by the memory device is used by the 
kernel, it
can't be offlined. It is not a bug.

Known problems:
1. memory can't be offlined when CONFIG_MEMCG is selected.
    For example: there is a memory device on node 1. The address range
    is [1G, 1.5G). You will find 4 new directories memory8, memory9, 
memory10,
    and memory11 under the directory /sys/devices/system/memory/.
    If CONFIG_MEMCG is selected, we will allocate memory to store 
page cgroup
    when we online pages. When we online memory8, the memory stored 
page cgroup
    is not provided by this memory device. But when we online 
memory9, the memory
    stored page cgroup may be provided by memory8. So we can't 
offline memory8
    now. We should offline the memory in the reversed order.
    When the memory device is hotremoved, we will auto offline 
memory provided
    by this memory device. But we don't know which memory is onlined 
first, so
    offlining memory may fail. In such case, you should offline the 
memory by
    hand before hotremoving the memory device.
2. hotremoving memory device may cause kernel panicked
    This bug will be fixed by Liu Jiang's patch:
    https://lkml.org/lkml/2012/7/3/1

change log of v9:
  [RFC PATCH v9 8/21]
    * add a lock to protect the list map_entries
    * add an indicator to firmware_map_entry to remember whether the 
memory
      is allocated from bootmem
  [RFC PATCH v9 10/21]
    * change the macro to inline function
  [RFC PATCH v9 19/21]
    * don't offline the node if the cpu on the node is onlined
  [RFC PATCH v9 21/21]
    * create new patch: auto offline page_cgroup when onlining 
memory block
      failed

change log of v8:
  [RFC PATCH v8 17/20]
    * Fix problems when one node's range include the other nodes
  [RFC PATCH v8 18/20]
    * fix building error when CONFIG_MEMORY_HOTPLUG_SPARSE or 
CONFIG_HUGETLBFS
      is not defined.
  [RFC PATCH v8 19/20]
    * don't offline node when some memory sections are not removed
  [RFC PATCH v8 20/20]
    * create new patch: clear hwpoisoned flag when onlining pages

change log of v7:
  [RFC PATCH v7 4/19]
    * do not continue if acpi_memory_device_remove_memory() fails.
  [RFC PATCH v7 15/19]
    * handle usemap in register_page_bootmem_info_section() too.

change log of v6:
  [RFC PATCH v6 12/19]
    * fix building error on other archtitectures than x86

  [RFC PATCH v6 15-16/19]
    * fix building error on other archtitectures than x86

change log of v5:
  * merge the patchset to clear page table and the patchset to hot 
remove
    memory(from ishimatsu) to one big patchset.

  [RFC PATCH v5 1/19]
    * rename remove_memory() to offline_memory()/offline_pages()

  [RFC PATCH v5 2/19]
    * new patch: implement offline_memory(). This function offlines 
pages,
      update memory block's state, and notify the userspace that the 
memory
      block's state is changed.

  [RFC PATCH v5 4/19]
    * offline and remove memory in acpi_memory_disable_device() too.

  [RFC PATCH v5 17/19]
    * new patch: add a new function __remove_zone() to revert the 
things done
      in the function __add_zone().

  [RFC PATCH v5 18/19]
    * flush work befor reseting node device.

change log of v4:
  * remove "memory-hotplug : unify argument of 
firmware_map_add_early/hotplug"
    from the patch series, since the patch is a bugfix. It is being 
disccussed
    on other thread. But for testing the patch series, the patch is 
needed.
    So I added the patch as [PATCH 0/13].

  [RFC PATCH v4 2/13]
    * check memory is online or not at remove_memory()
    * add memory_add_physaddr_to_nid() to 
acpi_memory_device_remove() for
      getting node id
  [RFC PATCH v4 3/13]
    * create new patch : check memory is online or not at 
online_pages()

  [RFC PATCH v4 4/13]
    * add __ref section to remove_memory()
    * call firmware_map_remove_entry() before 
remove_sysfs_fw_map_entry()

  [RFC PATCH v4 11/13]
    * rewrite register_page_bootmem_memmap() for removing page used 
as PT/PMD

change log of v3:
  * rebase to 3.5.0-rc6

  [RFC PATCH v2 2/13]
    * remove extra kobject_put()

    * The patch was commented by Wen. Wen's comment is
      "acpi_memory_device_remove() should ignore a return value of
      remove_memory() since caller does not care the return value".
      But I did not change it since I think caller should care the
      return value. And I am trying to fix it as follow:

      https://lkml.org/lkml/2012/7/5/624

  [RFC PATCH v2 4/13]
    * remove a firmware_memmap_entry allocated by kzmalloc()

change log of v2:
  [RFC PATCH v2 2/13]
    * check whether memory block is offline or not before calling 
offline_memory()
    * check whether section is valid or not in is_memblk_offline()
    * call kobject_put() for each memory_block in is_memblk_offline()

  [RFC PATCH v2 3/13]
    * unify the end argument of firmware_map_add_early/hotplug

  [RFC PATCH v2 4/13]
    * add release_firmware_map_entry() for freeing firmware_map_entry

  [RFC PATCH v2 6/13]
   * add release_memory_block() for freeing memory_block

  [RFC PATCH v2 11/13]
   * fix wrong arguments of free_pages()


Wen Congyang (8):
   memory-hotplug: implement offline_memory()
   memory-hotplug: store the node id in acpi_memory_device
   memory-hotplug: export the function acpi_bus_remove()
   memory-hotplug: call acpi_bus_remove() to remove memory device
   memory-hotplug: introduce new function arch_remove_memory()
   memory-hotplug: remove sysfs file of node
   memory-hotplug: clear hwpoisoned flag when onlining pages
   memory-hotplug: auto offline page_cgroup when onlining memory block
     failed

Yasuaki Ishimatsu (13):
   memory-hotplug: rename remove_memory() to
     offline_memory()/offline_pages()
   memory-hotplug: offline and remove memory when removing the memory
     device
   memory-hotplug: check whether memory is present or not
   memory-hotplug: remove /sys/firmware/memmap/X sysfs
   memory-hotplug: does not release memory region in PAGES_PER_SECTION
     chunks
   memory-hotplug: add memory_block_release
   memory-hotplug: remove_memory calls __remove_pages
   memory-hotplug: check page type in get_page_bootmem
   memory-hotplug: move register_page_bootmem_info_node and
     put_page_bootmem for sparse-vmemmap
   memory-hotplug: implement register_page_bootmem_info_section of
     sparse-vmemmap
   memory-hotplug: free memmap of sparse-vmemmap
   memory_hotplug: clear zone when the memory is removed
   memory-hotplug: add node_device_release

  arch/ia64/mm/discontig.c                        |   14 +
  arch/ia64/mm/init.c                             |   16 +
  arch/powerpc/mm/init_64.c                       |   14 +
  arch/powerpc/mm/mem.c                           |   14 +
  arch/powerpc/platforms/pseries/hotplug-memory.c |   16 +-
  arch/s390/mm/init.c                             |   12 +
  arch/s390/mm/vmem.c                             |   14 +
  arch/sh/mm/init.c                               |   15 +
  arch/sparc/mm/init_64.c                         |   14 +
  arch/tile/mm/init.c                             |    8 +
  arch/x86/include/asm/pgtable_types.h            |    1 +
  arch/x86/mm/init_32.c                           |   10 +
  arch/x86/mm/init_64.c                           |  331 
++++++++++++++++++
  arch/x86/mm/pageattr.c                          |   47 ++--
  drivers/acpi/acpi_memhotplug.c                  |   54 +++-
  drivers/acpi/scan.c                             |    3 +-
  drivers/base/memory.c                           |   88 ++++-
  drivers/base/node.c                             |   11 +
  drivers/firmware/memmap.c                       |   98 +++++-
  include/acpi/acpi_bus.h                         |    1 +
  include/linux/firmware-map.h                    |    6 +
  include/linux/memory.h                          |    5 +
  include/linux/memory_hotplug.h                  |   25 +-
  include/linux/mm.h                              |    5 +-
  include/linux/mmzone.h                          |   19 +
  mm/memory_hotplug.c                             |  424 
+++++++++++++++++++++--
  mm/page_cgroup.c                                |    3 +
  mm/sparse.c                                     |    5 +-
  28 files changed, 1181 insertions(+), 92 deletions(-)

-- 
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Yasuaki Ishimatsu <hidden>
Date: 2012-10-02 00:03:42

Hi Chen,

2012/10/02 8:45, Ni zhan Chen wrote:
On 10/01/2012 12:44 PM, Yasuaki Ishimatsu wrote:
quoted
Hi Chen,

2012/09/29 17:19, Ni zhan Chen wrote:
quoted
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Wen Congyang <redacted>

This patch series aims to support physical memory hot-remove.

The patches can free/remove the following things:

   - acpi_memory_info                          : [RFC PATCH 4/19]
   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19]
   - iomem_resource                            : [RFC PATCH 9/19]
   - mem_section and related sysfs files       : [RFC PATCH 10-11, 13-16/19]
   - page table of removed memory              : [RFC PATCH 12/19]
   - node and related sysfs files              : [RFC PATCH 18-19/19]

If you find lack of function for physical memory hot-remove, please let me
know.

How to test this patchset?
1. apply this patchset and build the kernel. MEMORY_HOTPLUG, MEMORY_HOTREMOVE,
    ACPI_HOTPLUG_MEMORY must be selected.
2. load the module acpi_memhotplug
Hi Yasuaki,

where is the acpi_memhotplug module?
If you build acpi_memhotplug as module, it is created under
/lib/modules/<kernel-version>/driver/acpi/ directory. It depends
on config ACPI_HOTPLUG_MEMORY. The confing is [*], it becomes built-in
function. So you don't need to care about it.
Thanks,
Yasuaki Ishimatsu
Hi Yasuaki,

I build the kernel, MEMORY_HOTPLUG, MEMORY_HOTREMOVE, ACPI_HOTPLUG_MEMORY are seleted as [*], but I can't find PNP0C80:XX under the directory /sys/bus/acpi/devices/.

[root@localhost ~]# ls /sys/bus/acpi/devices/
device:00  device:07  device:0e  device:15  device:1c  device:23 device:2a   LNXCPU:00  LNXCPU:07    PNP0501:00  PNP0C02:00 PNP0C0F:02 PNP0C14:01
device:01  device:08  device:0f  device:16  device:1d  device:24 device:2b   LNXCPU:01  LNXPWRBN:00  PNP0800:00  PNP0C02:01 PNP0C0F:03 PNP0C31:00
device:02  device:09  device:10  device:17  device:1e  device:25 device:2c   LNXCPU:02  LNXSYSTM:00  PNP0A08:00  PNP0C02:02 PNP0C0F:04
device:03  device:0a  device:11  device:18  device:1f  device:26 device:2d   LNXCPU:03  PNP0000:00   PNP0B00:00  PNP0C04:00 PNP0C0F:05
device:04  device:0b  device:12  device:19  device:20  device:27 device:2e   LNXCPU:04  PNP0100:00   PNP0C01:00  PNP0C0C:00 PNP0C0F:06
device:05  device:0c  device:13  device:1a  device:21  device:28 device:2f   LNXCPU:05  PNP0103:00   PNP0C01:01  PNP0C0F:00 PNP0C0F:07
device:06  device:0d  device:14  device:1b  device:22  device:29 INT3F0D:00  LNXCPU:06  PNP0200:00   PNP0C01:02  PNP0C0F:01 PNP0C14:00

then what I miss ? thanks.
It depend on hardware. It seems that your system does not support
memory hotplug. If you use KVM, you can try memory hotplug on KVM
guest by applying Vasilis' patch-set.

http://lists.gnu.org/archive/html/qemu-devel/2012-07/msg01389.html

Thanks,
Yasuaki Ishimatsu
quoted
quoted
quoted
3. hotplug the memory device(it depends on your hardware)
    You will see the memory device under the directory /sys/bus/acpi/devices/.
    Its name is PNP0C80:XX.
4. online/offline pages provided by this memory device
    You can write online/offline to /sys/devices/system/memory/memoryX/state to
    online/offline pages provided by this memory device
5. hotremove the memory device
    You can hotremove the memory device by the hardware, or writing 1 to
    /sys/bus/acpi/devices/PNP0C80:XX/eject.

Note: if the memory provided by the memory device is used by the kernel, it
can't be offlined. It is not a bug.

Known problems:
1. memory can't be offlined when CONFIG_MEMCG is selected.
    For example: there is a memory device on node 1. The address range
    is [1G, 1.5G). You will find 4 new directories memory8, memory9, memory10,
    and memory11 under the directory /sys/devices/system/memory/.
    If CONFIG_MEMCG is selected, we will allocate memory to store page cgroup
    when we online pages. When we online memory8, the memory stored page cgroup
    is not provided by this memory device. But when we online memory9, the memory
    stored page cgroup may be provided by memory8. So we can't offline memory8
    now. We should offline the memory in the reversed order.
    When the memory device is hotremoved, we will auto offline memory provided
    by this memory device. But we don't know which memory is onlined first, so
    offlining memory may fail. In such case, you should offline the memory by
    hand before hotremoving the memory device.
2. hotremoving memory device may cause kernel panicked
    This bug will be fixed by Liu Jiang's patch:
    https://lkml.org/lkml/2012/7/3/1

change log of v9:
  [RFC PATCH v9 8/21]
    * add a lock to protect the list map_entries
    * add an indicator to firmware_map_entry to remember whether the memory
      is allocated from bootmem
  [RFC PATCH v9 10/21]
    * change the macro to inline function
  [RFC PATCH v9 19/21]
    * don't offline the node if the cpu on the node is onlined
  [RFC PATCH v9 21/21]
    * create new patch: auto offline page_cgroup when onlining memory block
      failed

change log of v8:
  [RFC PATCH v8 17/20]
    * Fix problems when one node's range include the other nodes
  [RFC PATCH v8 18/20]
    * fix building error when CONFIG_MEMORY_HOTPLUG_SPARSE or CONFIG_HUGETLBFS
      is not defined.
  [RFC PATCH v8 19/20]
    * don't offline node when some memory sections are not removed
  [RFC PATCH v8 20/20]
    * create new patch: clear hwpoisoned flag when onlining pages

change log of v7:
  [RFC PATCH v7 4/19]
    * do not continue if acpi_memory_device_remove_memory() fails.
  [RFC PATCH v7 15/19]
    * handle usemap in register_page_bootmem_info_section() too.

change log of v6:
  [RFC PATCH v6 12/19]
    * fix building error on other archtitectures than x86

  [RFC PATCH v6 15-16/19]
    * fix building error on other archtitectures than x86

change log of v5:
  * merge the patchset to clear page table and the patchset to hot remove
    memory(from ishimatsu) to one big patchset.

  [RFC PATCH v5 1/19]
    * rename remove_memory() to offline_memory()/offline_pages()

  [RFC PATCH v5 2/19]
    * new patch: implement offline_memory(). This function offlines pages,
      update memory block's state, and notify the userspace that the memory
      block's state is changed.

  [RFC PATCH v5 4/19]
    * offline and remove memory in acpi_memory_disable_device() too.

  [RFC PATCH v5 17/19]
    * new patch: add a new function __remove_zone() to revert the things done
      in the function __add_zone().

  [RFC PATCH v5 18/19]
    * flush work befor reseting node device.

change log of v4:
  * remove "memory-hotplug : unify argument of firmware_map_add_early/hotplug"
    from the patch series, since the patch is a bugfix. It is being disccussed
    on other thread. But for testing the patch series, the patch is needed.
    So I added the patch as [PATCH 0/13].

  [RFC PATCH v4 2/13]
    * check memory is online or not at remove_memory()
    * add memory_add_physaddr_to_nid() to acpi_memory_device_remove() for
      getting node id
  [RFC PATCH v4 3/13]
    * create new patch : check memory is online or not at online_pages()

  [RFC PATCH v4 4/13]
    * add __ref section to remove_memory()
    * call firmware_map_remove_entry() before remove_sysfs_fw_map_entry()

  [RFC PATCH v4 11/13]
    * rewrite register_page_bootmem_memmap() for removing page used as PT/PMD

change log of v3:
  * rebase to 3.5.0-rc6

  [RFC PATCH v2 2/13]
    * remove extra kobject_put()

    * The patch was commented by Wen. Wen's comment is
      "acpi_memory_device_remove() should ignore a return value of
      remove_memory() since caller does not care the return value".
      But I did not change it since I think caller should care the
      return value. And I am trying to fix it as follow:

      https://lkml.org/lkml/2012/7/5/624

  [RFC PATCH v2 4/13]
    * remove a firmware_memmap_entry allocated by kzmalloc()

change log of v2:
  [RFC PATCH v2 2/13]
    * check whether memory block is offline or not before calling offline_memory()
    * check whether section is valid or not in is_memblk_offline()
    * call kobject_put() for each memory_block in is_memblk_offline()

  [RFC PATCH v2 3/13]
    * unify the end argument of firmware_map_add_early/hotplug

  [RFC PATCH v2 4/13]
    * add release_firmware_map_entry() for freeing firmware_map_entry

  [RFC PATCH v2 6/13]
   * add release_memory_block() for freeing memory_block

  [RFC PATCH v2 11/13]
   * fix wrong arguments of free_pages()


Wen Congyang (8):
   memory-hotplug: implement offline_memory()
   memory-hotplug: store the node id in acpi_memory_device
   memory-hotplug: export the function acpi_bus_remove()
   memory-hotplug: call acpi_bus_remove() to remove memory device
   memory-hotplug: introduce new function arch_remove_memory()
   memory-hotplug: remove sysfs file of node
   memory-hotplug: clear hwpoisoned flag when onlining pages
   memory-hotplug: auto offline page_cgroup when onlining memory block
     failed

Yasuaki Ishimatsu (13):
   memory-hotplug: rename remove_memory() to
     offline_memory()/offline_pages()
   memory-hotplug: offline and remove memory when removing the memory
     device
   memory-hotplug: check whether memory is present or not
   memory-hotplug: remove /sys/firmware/memmap/X sysfs
   memory-hotplug: does not release memory region in PAGES_PER_SECTION
     chunks
   memory-hotplug: add memory_block_release
   memory-hotplug: remove_memory calls __remove_pages
   memory-hotplug: check page type in get_page_bootmem
   memory-hotplug: move register_page_bootmem_info_node and
     put_page_bootmem for sparse-vmemmap
   memory-hotplug: implement register_page_bootmem_info_section of
     sparse-vmemmap
   memory-hotplug: free memmap of sparse-vmemmap
   memory_hotplug: clear zone when the memory is removed
   memory-hotplug: add node_device_release

  arch/ia64/mm/discontig.c                        |   14 +
  arch/ia64/mm/init.c                             |   16 +
  arch/powerpc/mm/init_64.c                       |   14 +
  arch/powerpc/mm/mem.c                           |   14 +
  arch/powerpc/platforms/pseries/hotplug-memory.c |   16 +-
  arch/s390/mm/init.c                             |   12 +
  arch/s390/mm/vmem.c                             |   14 +
  arch/sh/mm/init.c                               |   15 +
  arch/sparc/mm/init_64.c                         |   14 +
  arch/tile/mm/init.c                             |    8 +
  arch/x86/include/asm/pgtable_types.h            |    1 +
  arch/x86/mm/init_32.c                           |   10 +
  arch/x86/mm/init_64.c                           |  331 ++++++++++++++++++
  arch/x86/mm/pageattr.c                          |   47 ++--
  drivers/acpi/acpi_memhotplug.c                  |   54 +++-
  drivers/acpi/scan.c                             |    3 +-
  drivers/base/memory.c                           |   88 ++++-
  drivers/base/node.c                             |   11 +
  drivers/firmware/memmap.c                       |   98 +++++-
  include/acpi/acpi_bus.h                         |    1 +
  include/linux/firmware-map.h                    |    6 +
  include/linux/memory.h                          |    5 +
  include/linux/memory_hotplug.h                  |   25 +-
  include/linux/mm.h                              |    5 +-
  include/linux/mmzone.h                          |   19 +
  mm/memory_hotplug.c                             |  424 +++++++++++++++++++++--
  mm/page_cgroup.c                                |    3 +
  mm/sparse.c                                     |    5 +-
  28 files changed, 1181 insertions(+), 92 deletions(-)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: [RFC v9 PATCH 06/21] memory-hotplug: export the function acpi_bus_remove()

From: Ni zhan Chen <hidden>
Date: 2012-10-02 00:34:55

On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
From: Wen Congyang <redacted>

The function acpi_bus_remove() can remove a acpi device from acpi device.
IIUC, s/acpi device/acpi bus
quoted hunk
  
When a acpi device is removed, we need to call this function to remove
the acpi device from acpi bus. So export this function.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Yasuaki Ishimatsu <redacted>
Signed-off-by: Wen Congyang <redacted>
---
  drivers/acpi/scan.c     |    3 ++-
  include/acpi/acpi_bus.h |    1 +
  2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index d1ecca2..1cefc34 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -1224,7 +1224,7 @@ static int acpi_device_set_context(struct acpi_device *device)
  	return -ENODEV;
  }
  
-static int acpi_bus_remove(struct acpi_device *dev, int rmdevice)
+int acpi_bus_remove(struct acpi_device *dev, int rmdevice)
  {
  	if (!dev)
  		return -EINVAL;
@@ -1246,6 +1246,7 @@ static int acpi_bus_remove(struct acpi_device *dev, int rmdevice)
  
  	return 0;
  }
+EXPORT_SYMBOL(acpi_bus_remove);
  
  static int acpi_add_single_object(struct acpi_device **child,
  				  acpi_handle handle, int type,
diff --git a/include/acpi/acpi_bus.h b/include/acpi/acpi_bus.h
index bde976e..2ccf109 100644
--- a/include/acpi/acpi_bus.h
+++ b/include/acpi/acpi_bus.h
@@ -360,6 +360,7 @@ bool acpi_bus_power_manageable(acpi_handle handle);
  bool acpi_bus_can_wakeup(acpi_handle handle);
  int acpi_power_resource_register_device(struct device *dev, acpi_handle handle);
  void acpi_power_resource_unregister_device(struct device *dev, acpi_handle handle);
+int acpi_bus_remove(struct acpi_device *dev, int rmdevice);
  #ifdef CONFIG_ACPI_PROC_EVENT
  int acpi_bus_generate_proc_event(struct acpi_device *device, u8 type, int data);
  int acpi_bus_generate_proc_event4(const char *class, const char *bid, u8 type, int data);

Re: [RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages()

From: Yasuaki Ishimatsu <hidden>
Date: 2012-10-02 01:20:14

Hi Kosaki-san,

2012/09/29 7:15, KOSAKI Motohiro wrote:
On Thu, Sep 27, 2012 at 11:50 PM, Yasuaki Ishimatsu
[off-list ref] wrote:
quoted
Hi Chen,


2012/09/28 11:22, Ni zhan Chen wrote:
quoted
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

remove_memory() only try to offline pages. It is called in two cases:
1. hot remove a memory device
2. echo offline >/sys/devices/system/memory/memoryXX/state

In the 1st case, we should also change memory block's state, and notify
the userspace that the memory block's state is changed after offlining
pages.

So rename remove_memory() to offline_memory()/offline_pages(). And in
the 1st case, offline_memory() will be used. The function
offline_memory()
is not implemented. In the 2nd case, offline_pages() will be used.

But this time there is not a function associated with add_memory.

To associate with add_memory() later, we renamed it.
Then, you introduced bisect breakage. It is definitely unacceptable.
What is "bisect breakage" meaning?

Thanks,
Yasuaki Ishimatsu
NAK.

Re: [RFC v9 PATCH 16/21] memory-hotplug: free memmap of sparse-vmemmap

From: Ni zhan Chen <hidden>
Date: 2012-10-02 04:22:12

On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted hunk
From: Yasuaki Ishimatsu <redacted>

All pages of virtual mapping in removed memory cannot be freed, since some pages
used as PGD/PUD includes not only removed memory but also other memory. So the
patch checks whether page can be freed or not.

How to check whether page can be freed or not?
  1. When removing memory, the page structs of the revmoved memory are filled
     with 0FD.
  2. All page structs are filled with 0xFD on PT/PMD, PT/PMD can be cleared.
     In this case, the page used as PT/PMD can be freed.

Applying patch, __remove_section() of CONFIG_SPARSEMEM_VMEMMAP is integrated
into one. So __remove_section() of CONFIG_SPARSEMEM_VMEMMAP is deleted.

Note:  vmemmap_kfree() and vmemmap_free_bootmem() are not implemented for ia64,
ppc, s390, and sparc.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  arch/ia64/mm/discontig.c  |    8 +++
  arch/powerpc/mm/init_64.c |    8 +++
  arch/s390/mm/vmem.c       |    8 +++
  arch/sparc/mm/init_64.c   |    8 +++
  arch/x86/mm/init_64.c     |  119 +++++++++++++++++++++++++++++++++++++++++++++
  include/linux/mm.h        |    2 +
  mm/memory_hotplug.c       |   17 +------
  mm/sparse.c               |    5 +-
  8 files changed, 158 insertions(+), 17 deletions(-)
diff --git a/arch/ia64/mm/discontig.c b/arch/ia64/mm/discontig.c
index 33943db..0d23b69 100644
--- a/arch/ia64/mm/discontig.c
+++ b/arch/ia64/mm/discontig.c
@@ -823,6 +823,14 @@ int __meminit vmemmap_populate(struct page *start_page,
  	return vmemmap_populate_basepages(start_page, size, node);
  }
  
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
  				  struct page *start_page, unsigned long size)
  {
diff --git a/arch/powerpc/mm/init_64.c b/arch/powerpc/mm/init_64.c
index 3690c44..835a2b3 100644
--- a/arch/powerpc/mm/init_64.c
+++ b/arch/powerpc/mm/init_64.c
@@ -299,6 +299,14 @@ int __meminit vmemmap_populate(struct page *start_page,
  	return 0;
  }
  
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
  				  struct page *start_page, unsigned long size)
  {
diff --git a/arch/s390/mm/vmem.c b/arch/s390/mm/vmem.c
index eda55cd..4b42b0b 100644
--- a/arch/s390/mm/vmem.c
+++ b/arch/s390/mm/vmem.c
@@ -227,6 +227,14 @@ out:
  	return ret;
  }
  
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
  				  struct page *start_page, unsigned long size)
  {
diff --git a/arch/sparc/mm/init_64.c b/arch/sparc/mm/init_64.c
index add1cc7..1384826 100644
--- a/arch/sparc/mm/init_64.c
+++ b/arch/sparc/mm/init_64.c
@@ -2078,6 +2078,14 @@ void __meminit vmemmap_populate_print_last(void)
  	}
  }
  
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
  				  struct page *start_page, unsigned long size)
  {
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 0075592..4e8f8a4 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -1138,6 +1138,125 @@ vmemmap_populate(struct page *start_page, unsigned long size, int node)
  	return 0;
  }
  
+#define PAGE_INUSE 0xFD
+
+unsigned long find_and_clear_pte_page(unsigned long addr, unsigned long end,
+			    struct page **pp, int *page_size)
+{
+	pgd_t *pgd;
+	pud_t *pud;
+	pmd_t *pmd;
+	pte_t *pte;
+	void *page_addr;
+	unsigned long next;
+
+	*pp = NULL;
+
+	pgd = pgd_offset_k(addr);
+	if (pgd_none(*pgd))
+		return pgd_addr_end(addr, end);
+
+	pud = pud_offset(pgd, addr);
+	if (pud_none(*pud))
+		return pud_addr_end(addr, end);
+
+	if (!cpu_has_pse) {
+		next = (addr + PAGE_SIZE) & PAGE_MASK;
+		pmd = pmd_offset(pud, addr);
+		if (pmd_none(*pmd))
+			return next;
+
+		pte = pte_offset_kernel(pmd, addr);
+		if (pte_none(*pte))
+			return next;
+
+		*page_size = PAGE_SIZE;
+		*pp = pte_page(*pte);
+	} else {
+		next = pmd_addr_end(addr, end);
+
+		pmd = pmd_offset(pud, addr);
+		if (pmd_none(*pmd))
+			return next;
+
+		*page_size = PMD_SIZE;
+		*pp = pmd_page(*pmd);
+	}
+
+	/*
+	 * Removed page structs are filled with 0xFD.
+	 */
+	memset((void *)addr, PAGE_INUSE, next - addr);
+
+	page_addr = page_address(*pp);
+
+	/*
+	 * Check the page is filled with 0xFD or not.
+	 * memchr_inv() returns the address. In this case, we cannot
+	 * clear PTE/PUD entry, since the page is used by other.
+	 * So we cannot also free the page.
+	 *
+	 * memchr_inv() returns NULL. In this case, we can clear
+	 * PTE/PUD entry, since the page is not used by other.
+	 * So we can also free the page.
+	 */
+	if (memchr_inv(page_addr, PAGE_INUSE, *page_size)) {
+		*pp = NULL;
+		return next;
+	}
+
Hi Yasuaki,

why call memchr_inv check after memset, this time the page can always be 
filled with 0xFD.
quoted hunk
+	if (!cpu_has_pse)
+		pte_clear(&init_mm, addr, pte);
+	else
+		pmd_clear(pmd);
+
+	return next;
+}
+
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+	unsigned long addr = (unsigned long)memmap;
+	unsigned long end = (unsigned long)(memmap + nr_pages);
+	unsigned long next;
+	struct page *page;
+	int page_size;
+
+	for (; addr < end; addr = next) {
+		page = NULL;
+		page_size = 0;
+		next = find_and_clear_pte_page(addr, end, &page, &page_size);
+		if (!page)
+			continue;
+
+		free_pages((unsigned long)page_address(page),
+			    get_order(page_size));
+		__flush_tlb_one(addr);
+	}
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+	unsigned long addr = (unsigned long)memmap;
+	unsigned long end = (unsigned long)(memmap + nr_pages);
+	unsigned long next;
+	struct page *page;
+	int page_size;
+	unsigned long magic;
+
+	for (; addr < end; addr = next) {
+		page = NULL;
+		page_size = 0;
+		next = find_and_clear_pte_page(addr, end, &page, &page_size);
+		if (!page)
+			continue;
+
+		magic = (unsigned long) page->lru.next;
+		if (magic == SECTION_INFO)
+			put_page_bootmem(page);
+		flush_tlb_kernel_range(addr, end);
+	}
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
  				  struct page *start_page, unsigned long size)
  {
diff --git a/include/linux/mm.h b/include/linux/mm.h
index c607913..fb0d1fc 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1620,6 +1620,8 @@ int vmemmap_populate(struct page *start_page, unsigned long pages, int node);
  void vmemmap_populate_print_last(void);
  void register_page_bootmem_memmap(unsigned long section_nr, struct page *map,
  				  unsigned long size);
+void vmemmap_kfree(struct page *memmpa, unsigned long nr_pages);
+void vmemmap_free_bootmem(struct page *memmpa, unsigned long nr_pages);
  
  enum mf_flags {
  	MF_COUNT_INCREASED = 1 << 0,
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 647a7f2..c54922c 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -308,19 +308,6 @@ static int __meminit __add_section(int nid, struct zone *zone,
  	return register_new_memory(nid, __pfn_to_section(phys_start_pfn));
  }
  
-#ifdef CONFIG_SPARSEMEM_VMEMMAP
-static int __remove_section(struct zone *zone, struct mem_section *ms)
-{
-	int ret = -EINVAL;
-
-	if (!valid_section(ms))
-		return ret;
-
-	ret = unregister_memory_section(ms);
-
-	return ret;
-}
-#else
  static int __remove_section(struct zone *zone, struct mem_section *ms)
  {
  	unsigned long flags;
@@ -337,9 +324,9 @@ static int __remove_section(struct zone *zone, struct mem_section *ms)
  	pgdat_resize_lock(pgdat, &flags);
  	sparse_remove_one_section(zone, ms);
  	pgdat_resize_unlock(pgdat, &flags);
-	return 0;
+
+	return ret;
  }
-#endif
  
  /*
   * Reasonably generic function for adding memory.  It is
diff --git a/mm/sparse.c b/mm/sparse.c
index fac95f2..ab9d755 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -613,12 +613,13 @@ static inline struct page *kmalloc_section_memmap(unsigned long pnum, int nid,
  	/* This will make the necessary allocations eventually. */
  	return sparse_mem_map_populate(pnum, nid);
  }
-static void __kfree_section_memmap(struct page *memmap, unsigned long nr_pages)
+static void __kfree_section_memmap(struct page *page, unsigned long nr_pages)
  {
-	return; /* XXX: Not implemented yet */
+	vmemmap_kfree(page, nr_pages);
  }
  static void free_map_bootmem(struct page *page, unsigned long nr_pages)
  {
+	vmemmap_free_bootmem(page, nr_pages);
  }
  #else
  static struct page *__kmalloc_section_memmap(unsigned long nr_pages)

Re: [RFC v9 PATCH 13/21] memory-hotplug: check page type in get_page_bootmem

From: Ni zhan Chen <hidden>
Date: 2012-10-02 12:24:19

On 10/01/2012 11:03 AM, Yasuaki Ishimatsu wrote:
Hi Chen,

2012/09/29 11:15, Ni zhan Chen wrote:
quoted
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

The function get_page_bootmem() may be called more than one time to 
the same
page. There is no need to set page's type, private if the function 
is not
the first time called to the page.

Note: the patch is just optimization and does not fix any problem.
Hi Yasuaki,

this patch is reasonable to me. I have another question associated to 
get_page_bootmem(), the question is from another fujitsu guy's patch 
changelog [commit : 04753278769f3], the changelog said  that:

  1) When the memmap of removing section is allocated on other
      section by bootmem, it should/can be free.
  2) When the memmap of removing section is allocated on the
      same section, it shouldn't be freed. Because the section has to be
      logical memory offlined already and all pages must be isolated 
against
      page allocater. If it is freed, page allocator may use it which 
will
      be removed physically soon.

but I don't see his patch guarantee 2), it means that his patch 
doesn't guarantee the memmap of removing section which is allocated 
on other section by bootmem doesn't be freed. Hopefully get your 
explaination in details, thanks in advance. :-)
In my understanding, the patch does not guarantee it.
Please see [commit : 0c0a4a517a31e]. free_map_bootmem() in the commit
guarantees it.
Thanks Yasuaki, I have already seen the commit you mentioned. But the 
changelog of the commit I point out 2), why it said that "If it is 
freed, page allocator may use it which will be removed physically soon", 
does it mean that use-after-free ? AFAK, the isolated pages will be free 
if no users use it, so why not free the associated memmap?
Thanks,
Yasuaki Ishimatsu
quoted
quoted
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  mm/memory_hotplug.c |   15 +++++++++++----
  1 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index d736df3..26a5012 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -95,10 +95,17 @@ static void release_memory_resource(struct 
resource *res)
  static void get_page_bootmem(unsigned long info,  struct page *page,
                   unsigned long type)
  {
-    page->lru.next = (struct list_head *) type;
-    SetPagePrivate(page);
-    set_page_private(page, info);
-    atomic_inc(&page->_count);
+    unsigned long page_type;
+
+    page_type = (unsigned long)page->lru.next;
+    if (page_type < MEMORY_HOTPLUG_MIN_BOOTMEM_TYPE ||
+        page_type > MEMORY_HOTPLUG_MAX_BOOTMEM_TYPE){
+        page->lru.next = (struct list_head *)type;
+        SetPagePrivate(page);
+        set_page_private(page, info);
+        atomic_inc(&page->_count);
+    } else
+        atomic_inc(&page->_count);
  }
  /* reference to __meminit __free_pages_bootmem is valid

Re: [RFC v9 PATCH 06/21] memory-hotplug: export the function acpi_bus_remove()

From: KOSAKI Motohiro <hidden>
Date: 2012-10-02 17:28:48

On Mon, Oct 1, 2012 at 8:34 PM, Ni zhan Chen [off-list ref] wrote:
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Wen Congyang <redacted>

The function acpi_bus_remove() can remove a acpi device from acpi device.
IIUC, s/acpi device/acpi bus
IIUC, acpi_bus_remove() mean "remove the device from a bus".

Re: [RFC v9 PATCH 01/21] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages()

From: KOSAKI Motohiro <hidden>
Date: 2012-10-02 17:29:43

quoted
Then, you introduced bisect breakage. It is definitely unacceptable.
What is "bisect breakage" meaning?
Think what's happen when only applying path [1/21].

Re: [RFC v9 PATCH 16/21] memory-hotplug: free memmap of sparse-vmemmap

From: Yasuaki Ishimatsu <hidden>
Date: 2012-10-04 06:27:32

Hi Chen,

Sorry for late reply.

2012/10/02 13:21, Ni zhan Chen wrote:
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

All pages of virtual mapping in removed memory cannot be freed, since some pages
used as PGD/PUD includes not only removed memory but also other memory. So the
patch checks whether page can be freed or not.

How to check whether page can be freed or not?
  1. When removing memory, the page structs of the revmoved memory are filled
     with 0FD.
  2. All page structs are filled with 0xFD on PT/PMD, PT/PMD can be cleared.
     In this case, the page used as PT/PMD can be freed.

Applying patch, __remove_section() of CONFIG_SPARSEMEM_VMEMMAP is integrated
into one. So __remove_section() of CONFIG_SPARSEMEM_VMEMMAP is deleted.

Note:  vmemmap_kfree() and vmemmap_free_bootmem() are not implemented for ia64,
ppc, s390, and sparc.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  arch/ia64/mm/discontig.c  |    8 +++
  arch/powerpc/mm/init_64.c |    8 +++
  arch/s390/mm/vmem.c       |    8 +++
  arch/sparc/mm/init_64.c   |    8 +++
  arch/x86/mm/init_64.c     |  119 +++++++++++++++++++++++++++++++++++++++++++++
  include/linux/mm.h        |    2 +
  mm/memory_hotplug.c       |   17 +------
  mm/sparse.c               |    5 +-
  8 files changed, 158 insertions(+), 17 deletions(-)
diff --git a/arch/ia64/mm/discontig.c b/arch/ia64/mm/discontig.c
index 33943db..0d23b69 100644
--- a/arch/ia64/mm/discontig.c
+++ b/arch/ia64/mm/discontig.c
@@ -823,6 +823,14 @@ int __meminit vmemmap_populate(struct page *start_page,
      return vmemmap_populate_basepages(start_page, size, node);
  }
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/arch/powerpc/mm/init_64.c b/arch/powerpc/mm/init_64.c
index 3690c44..835a2b3 100644
--- a/arch/powerpc/mm/init_64.c
+++ b/arch/powerpc/mm/init_64.c
@@ -299,6 +299,14 @@ int __meminit vmemmap_populate(struct page *start_page,
      return 0;
  }
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/arch/s390/mm/vmem.c b/arch/s390/mm/vmem.c
index eda55cd..4b42b0b 100644
--- a/arch/s390/mm/vmem.c
+++ b/arch/s390/mm/vmem.c
@@ -227,6 +227,14 @@ out:
      return ret;
  }
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/arch/sparc/mm/init_64.c b/arch/sparc/mm/init_64.c
index add1cc7..1384826 100644
--- a/arch/sparc/mm/init_64.c
+++ b/arch/sparc/mm/init_64.c
@@ -2078,6 +2078,14 @@ void __meminit vmemmap_populate_print_last(void)
      }
  }
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 0075592..4e8f8a4 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -1138,6 +1138,125 @@ vmemmap_populate(struct page *start_page, unsigned long size, int node)
      return 0;
  }
+#define PAGE_INUSE 0xFD
+
+unsigned long find_and_clear_pte_page(unsigned long addr, unsigned long end,
+                struct page **pp, int *page_size)
+{
+    pgd_t *pgd;
+    pud_t *pud;
+    pmd_t *pmd;
+    pte_t *pte;
+    void *page_addr;
+    unsigned long next;
+
+    *pp = NULL;
+
+    pgd = pgd_offset_k(addr);
+    if (pgd_none(*pgd))
+        return pgd_addr_end(addr, end);
+
+    pud = pud_offset(pgd, addr);
+    if (pud_none(*pud))
+        return pud_addr_end(addr, end);
+
+    if (!cpu_has_pse) {
+        next = (addr + PAGE_SIZE) & PAGE_MASK;
+        pmd = pmd_offset(pud, addr);
+        if (pmd_none(*pmd))
+            return next;
+
+        pte = pte_offset_kernel(pmd, addr);
+        if (pte_none(*pte))
+            return next;
+
+        *page_size = PAGE_SIZE;
+        *pp = pte_page(*pte);
+    } else {
+        next = pmd_addr_end(addr, end);
+
+        pmd = pmd_offset(pud, addr);
+        if (pmd_none(*pmd))
+            return next;
+
+        *page_size = PMD_SIZE;
+        *pp = pmd_page(*pmd);
+    }
+
+    /*
+     * Removed page structs are filled with 0xFD.
+     */
+    memset((void *)addr, PAGE_INUSE, next - addr);
+
+    page_addr = page_address(*pp);
+
+    /*
+     * Check the page is filled with 0xFD or not.
+     * memchr_inv() returns the address. In this case, we cannot
+     * clear PTE/PUD entry, since the page is used by other.
+     * So we cannot also free the page.
+     *
+     * memchr_inv() returns NULL. In this case, we can clear
+     * PTE/PUD entry, since the page is not used by other.
+     * So we can also free the page.
+     */
+    if (memchr_inv(page_addr, PAGE_INUSE, *page_size)) {
+        *pp = NULL;
+        return next;
+    }
+
Hi Yasuaki,

why call memchr_inv check after memset, this time the page can always be filled with 0xFD.
The page is not always filled with 0xFD. find_and_clear_pte_page()
is calld in each section. So the function fills the page
section size/sizeof(page) byte with 0xFD one time. Thus if section size is
small, the page is filled with 0xFD.

Thanks,
Yasuaki Ishimatsu

  
quoted
+    if (!cpu_has_pse)
+        pte_clear(&init_mm, addr, pte);
+    else
+        pmd_clear(pmd);
+
+    return next;
+}
+
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+    unsigned long addr = (unsigned long)memmap;
+    unsigned long end = (unsigned long)(memmap + nr_pages);
+    unsigned long next;
+    struct page *page;
+    int page_size;
+
+    for (; addr < end; addr = next) {
+        page = NULL;
+        page_size = 0;
+        next = find_and_clear_pte_page(addr, end, &page, &page_size);
+        if (!page)
+            continue;
+
+        free_pages((unsigned long)page_address(page),
+                get_order(page_size));
+        __flush_tlb_one(addr);
+    }
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+    unsigned long addr = (unsigned long)memmap;
+    unsigned long end = (unsigned long)(memmap + nr_pages);
+    unsigned long next;
+    struct page *page;
+    int page_size;
+    unsigned long magic;
+
+    for (; addr < end; addr = next) {
+        page = NULL;
+        page_size = 0;
+        next = find_and_clear_pte_page(addr, end, &page, &page_size);
+        if (!page)
+            continue;
+
+        magic = (unsigned long) page->lru.next;
+        if (magic == SECTION_INFO)
+            put_page_bootmem(page);
+        flush_tlb_kernel_range(addr, end);
+    }
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/include/linux/mm.h b/include/linux/mm.h
index c607913..fb0d1fc 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1620,6 +1620,8 @@ int vmemmap_populate(struct page *start_page, unsigned long pages, int node);
  void vmemmap_populate_print_last(void);
  void register_page_bootmem_memmap(unsigned long section_nr, struct page *map,
                    unsigned long size);
+void vmemmap_kfree(struct page *memmpa, unsigned long nr_pages);
+void vmemmap_free_bootmem(struct page *memmpa, unsigned long nr_pages);
  enum mf_flags {
      MF_COUNT_INCREASED = 1 << 0,
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 647a7f2..c54922c 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -308,19 +308,6 @@ static int __meminit __add_section(int nid, struct zone *zone,
      return register_new_memory(nid, __pfn_to_section(phys_start_pfn));
  }
-#ifdef CONFIG_SPARSEMEM_VMEMMAP
-static int __remove_section(struct zone *zone, struct mem_section *ms)
-{
-    int ret = -EINVAL;
-
-    if (!valid_section(ms))
-        return ret;
-
-    ret = unregister_memory_section(ms);
-
-    return ret;
-}
-#else
  static int __remove_section(struct zone *zone, struct mem_section *ms)
  {
      unsigned long flags;
@@ -337,9 +324,9 @@ static int __remove_section(struct zone *zone, struct mem_section *ms)
      pgdat_resize_lock(pgdat, &flags);
      sparse_remove_one_section(zone, ms);
      pgdat_resize_unlock(pgdat, &flags);
-    return 0;
+
+    return ret;
  }
-#endif
  /*
   * Reasonably generic function for adding memory.  It is
diff --git a/mm/sparse.c b/mm/sparse.c
index fac95f2..ab9d755 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -613,12 +613,13 @@ static inline struct page *kmalloc_section_memmap(unsigned long pnum, int nid,
      /* This will make the necessary allocations eventually. */
      return sparse_mem_map_populate(pnum, nid);
  }
-static void __kfree_section_memmap(struct page *memmap, unsigned long nr_pages)
+static void __kfree_section_memmap(struct page *page, unsigned long nr_pages)
  {
-    return; /* XXX: Not implemented yet */
+    vmemmap_kfree(page, nr_pages);
  }
  static void free_map_bootmem(struct page *page, unsigned long nr_pages)
  {
+    vmemmap_free_bootmem(page, nr_pages);
  }
  #else
  static struct page *__kmalloc_section_memmap(unsigned long nr_pages)

Re: [RFC v9 PATCH 16/21] memory-hotplug: free memmap of sparse-vmemmap

From: Ni zhan Chen <hidden>
Date: 2012-10-06 14:18:44

On 10/04/2012 02:26 PM, Yasuaki Ishimatsu wrote:
Hi Chen,

Sorry for late reply.

2012/10/02 13:21, Ni zhan Chen wrote:
quoted
On 09/05/2012 05:25 PM, wency@cn.fujitsu.com wrote:
quoted
From: Yasuaki Ishimatsu <redacted>

All pages of virtual mapping in removed memory cannot be freed, 
since some pages
used as PGD/PUD includes not only removed memory but also other 
memory. So the
patch checks whether page can be freed or not.

How to check whether page can be freed or not?
  1. When removing memory, the page structs of the revmoved memory 
are filled
     with 0FD.
  2. All page structs are filled with 0xFD on PT/PMD, PT/PMD can be 
cleared.
     In this case, the page used as PT/PMD can be freed.

Applying patch, __remove_section() of CONFIG_SPARSEMEM_VMEMMAP is 
integrated
into one. So __remove_section() of CONFIG_SPARSEMEM_VMEMMAP is deleted.

Note:  vmemmap_kfree() and vmemmap_free_bootmem() are not 
implemented for ia64,
ppc, s390, and sparc.

CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <redacted>
CC: Len Brown <redacted>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <redacted>
CC: Christoph Lameter <redacted>
Cc: Minchan Kim <redacted>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <redacted>
CC: Wen Congyang <redacted>
Signed-off-by: Yasuaki Ishimatsu <redacted>
---
  arch/ia64/mm/discontig.c  |    8 +++
  arch/powerpc/mm/init_64.c |    8 +++
  arch/s390/mm/vmem.c       |    8 +++
  arch/sparc/mm/init_64.c   |    8 +++
  arch/x86/mm/init_64.c     |  119 
+++++++++++++++++++++++++++++++++++++++++++++
  include/linux/mm.h        |    2 +
  mm/memory_hotplug.c       |   17 +------
  mm/sparse.c               |    5 +-
  8 files changed, 158 insertions(+), 17 deletions(-)
diff --git a/arch/ia64/mm/discontig.c b/arch/ia64/mm/discontig.c
index 33943db..0d23b69 100644
--- a/arch/ia64/mm/discontig.c
+++ b/arch/ia64/mm/discontig.c
@@ -823,6 +823,14 @@ int __meminit vmemmap_populate(struct page 
*start_page,
      return vmemmap_populate_basepages(start_page, size, node);
  }
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/arch/powerpc/mm/init_64.c b/arch/powerpc/mm/init_64.c
index 3690c44..835a2b3 100644
--- a/arch/powerpc/mm/init_64.c
+++ b/arch/powerpc/mm/init_64.c
@@ -299,6 +299,14 @@ int __meminit vmemmap_populate(struct page 
*start_page,
      return 0;
  }
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/arch/s390/mm/vmem.c b/arch/s390/mm/vmem.c
index eda55cd..4b42b0b 100644
--- a/arch/s390/mm/vmem.c
+++ b/arch/s390/mm/vmem.c
@@ -227,6 +227,14 @@ out:
      return ret;
  }
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/arch/sparc/mm/init_64.c b/arch/sparc/mm/init_64.c
index add1cc7..1384826 100644
--- a/arch/sparc/mm/init_64.c
+++ b/arch/sparc/mm/init_64.c
@@ -2078,6 +2078,14 @@ void __meminit vmemmap_populate_print_last(void)
      }
  }
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index 0075592..4e8f8a4 100644
--- a/arch/x86/mm/init_64.c
+++ b/arch/x86/mm/init_64.c
@@ -1138,6 +1138,125 @@ vmemmap_populate(struct page *start_page, 
unsigned long size, int node)
      return 0;
  }
+#define PAGE_INUSE 0xFD
+
+unsigned long find_and_clear_pte_page(unsigned long addr, unsigned 
long end,
+                struct page **pp, int *page_size)
+{
+    pgd_t *pgd;
+    pud_t *pud;
+    pmd_t *pmd;
+    pte_t *pte;
+    void *page_addr;
+    unsigned long next;
+
+    *pp = NULL;
+
+    pgd = pgd_offset_k(addr);
+    if (pgd_none(*pgd))
+        return pgd_addr_end(addr, end);
+
+    pud = pud_offset(pgd, addr);
+    if (pud_none(*pud))
+        return pud_addr_end(addr, end);
+
+    if (!cpu_has_pse) {
+        next = (addr + PAGE_SIZE) & PAGE_MASK;
+        pmd = pmd_offset(pud, addr);
+        if (pmd_none(*pmd))
+            return next;
+
+        pte = pte_offset_kernel(pmd, addr);
+        if (pte_none(*pte))
+            return next;
+
+        *page_size = PAGE_SIZE;
+        *pp = pte_page(*pte);
+    } else {
+        next = pmd_addr_end(addr, end);
+
+        pmd = pmd_offset(pud, addr);
+        if (pmd_none(*pmd))
+            return next;
+
+        *page_size = PMD_SIZE;
+        *pp = pmd_page(*pmd);
+    }
+
+    /*
+     * Removed page structs are filled with 0xFD.
+     */
+    memset((void *)addr, PAGE_INUSE, next - addr);
+
+    page_addr = page_address(*pp);
+
+    /*
+     * Check the page is filled with 0xFD or not.
+     * memchr_inv() returns the address. In this case, we cannot
+     * clear PTE/PUD entry, since the page is used by other.
+     * So we cannot also free the page.
+     *
+     * memchr_inv() returns NULL. In this case, we can clear
+     * PTE/PUD entry, since the page is not used by other.
+     * So we can also free the page.
+     */
+    if (memchr_inv(page_addr, PAGE_INUSE, *page_size)) {
+        *pp = NULL;
+        return next;
+    }
+
Hi Yasuaki,

why call memchr_inv check after memset, this time the page can always 
be filled with 0xFD.
The page is not always filled with 0xFD. find_and_clear_pte_page()
is calld in each section. So the function fills the page
section size/sizeof(page) byte with 0xFD one time. Thus if section 
size is
small, the page is filled with 0xFD.
Hi Yasuaki,

But when section size will be small?

Regards,
Chen
Thanks,
Yasuaki Ishimatsu

quoted
quoted
+    if (!cpu_has_pse)
+        pte_clear(&init_mm, addr, pte);
+    else
+        pmd_clear(pmd);
+
+    return next;
+}
+
+void vmemmap_kfree(struct page *memmap, unsigned long nr_pages)
+{
+    unsigned long addr = (unsigned long)memmap;
+    unsigned long end = (unsigned long)(memmap + nr_pages);
+    unsigned long next;
+    struct page *page;
+    int page_size;
+
+    for (; addr < end; addr = next) {
+        page = NULL;
+        page_size = 0;
+        next = find_and_clear_pte_page(addr, end, &page, &page_size);
+        if (!page)
+            continue;
+
+        free_pages((unsigned long)page_address(page),
+                get_order(page_size));
+        __flush_tlb_one(addr);
+    }
+}
+
+void vmemmap_free_bootmem(struct page *memmap, unsigned long nr_pages)
+{
+    unsigned long addr = (unsigned long)memmap;
+    unsigned long end = (unsigned long)(memmap + nr_pages);
+    unsigned long next;
+    struct page *page;
+    int page_size;
+    unsigned long magic;
+
+    for (; addr < end; addr = next) {
+        page = NULL;
+        page_size = 0;
+        next = find_and_clear_pte_page(addr, end, &page, &page_size);
+        if (!page)
+            continue;
+
+        magic = (unsigned long) page->lru.next;
+        if (magic == SECTION_INFO)
+            put_page_bootmem(page);
+        flush_tlb_kernel_range(addr, end);
+    }
+}
+
  void register_page_bootmem_memmap(unsigned long section_nr,
                    struct page *start_page, unsigned long size)
  {
diff --git a/include/linux/mm.h b/include/linux/mm.h
index c607913..fb0d1fc 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1620,6 +1620,8 @@ int vmemmap_populate(struct page *start_page, 
unsigned long pages, int node);
  void vmemmap_populate_print_last(void);
  void register_page_bootmem_memmap(unsigned long section_nr, struct 
page *map,
                    unsigned long size);
+void vmemmap_kfree(struct page *memmpa, unsigned long nr_pages);
+void vmemmap_free_bootmem(struct page *memmpa, unsigned long 
nr_pages);
  enum mf_flags {
      MF_COUNT_INCREASED = 1 << 0,
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 647a7f2..c54922c 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -308,19 +308,6 @@ static int __meminit __add_section(int nid, 
struct zone *zone,
      return register_new_memory(nid, 
__pfn_to_section(phys_start_pfn));
  }
-#ifdef CONFIG_SPARSEMEM_VMEMMAP
-static int __remove_section(struct zone *zone, struct mem_section *ms)
-{
-    int ret = -EINVAL;
-
-    if (!valid_section(ms))
-        return ret;
-
-    ret = unregister_memory_section(ms);
-
-    return ret;
-}
-#else
  static int __remove_section(struct zone *zone, struct mem_section 
*ms)
  {
      unsigned long flags;
@@ -337,9 +324,9 @@ static int __remove_section(struct zone *zone, 
struct mem_section *ms)
      pgdat_resize_lock(pgdat, &flags);
      sparse_remove_one_section(zone, ms);
      pgdat_resize_unlock(pgdat, &flags);
-    return 0;
+
+    return ret;
  }
-#endif
  /*
   * Reasonably generic function for adding memory.  It is
diff --git a/mm/sparse.c b/mm/sparse.c
index fac95f2..ab9d755 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -613,12 +613,13 @@ static inline struct page 
*kmalloc_section_memmap(unsigned long pnum, int nid,
      /* This will make the necessary allocations eventually. */
      return sparse_mem_map_populate(pnum, nid);
  }
-static void __kfree_section_memmap(struct page *memmap, unsigned 
long nr_pages)
+static void __kfree_section_memmap(struct page *page, unsigned long 
nr_pages)
  {
-    return; /* XXX: Not implemented yet */
+    vmemmap_kfree(page, nr_pages);
  }
  static void free_map_bootmem(struct page *page, unsigned long 
nr_pages)
  {
+    vmemmap_free_bootmem(page, nr_pages);
  }
  #else
  static struct page *__kmalloc_section_memmap(unsigned long nr_pages)

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Wen Congyang <hidden>
Date: 2012-10-09 06:10:56

At 09/27/2012 12:46 AM, Vasilis Liaskovitis Wrote:
Hi,

I am testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

After succesfull hot-add and online, I am doing a hot-remove with "echo 1 > /sys/bus/acpi/devices/PNP/eject"
When I do the OSPM-eject, I often get slab corruption in "acpi-state" cache, or in other caches
I found the reason: when you do OSPM-eject, the kernel will auto offline and remove the memory.
But, offlining memory fails, and the memory is still used by the kernel. But device_release_driver()
doesn't tell this error to the caller acpi_bus_remove(). The kernel will poweroff and eject
the device by emulate _PS3 and _EJ0. The kernel uses some memory which doesn't exist. It's
very dangerous.

Thanks
Wen Conyang
[  170.566995] Slab corruption (Not tainted): Acpi-State start=ffff88009fc1e548, len=80
[  170.567265] Redzone: 0x0/0x0.
[  170.567399] Last user: [<          (null)>](0x0)
[  170.567667] 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568078] 010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568487] 020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568894] 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569302] 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569712] Prev obj: start=000000009fc1e4d0, len=80
[  170.569869] BUG: unable to handle kernel paging request at 000000009fc1e520
[  170.570171] IP: [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.570397] PGD 7cf37067 PUD 0 
[  170.570619] Oops: 0000 [#1] SMP 
[  170.570843] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis microcode tpm tpm_bios psmouse parport_pc serio_raw evdev parport i2c_piix4 processor thermal_sys i2c_core button ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net virtio_blk ata_piix libata scsi_mod virtio_pci virtio_ring virtio
[  170.573474] CPU 0 
[  170.573568] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[  170.573830] RIP: 0010:[<ffffffff8112803c>]  [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.574106] RSP: 0018:ffff88003eaf3a70  EFLAGS: 00010202
[  170.574268] RAX: 000000009fc1e4c8 RBX: 0000000000000002 RCX: 00000000000024b8
[  170.574468] RDX: 000000009fc1e4c8 RSI: 000000009fc1e4c8 RDI: ffff88003e9bb980
[  170.574668] RBP: ffff88003e9bb980 R08: ffff880037964078 R09: 0000000000000000
[  170.574870] R10: 000000000000021e R11: 0000000000000002 R12: 000000009fc1e4c8
[  170.575070] R13: 000000009fc1e520 R14: 000000000000004f R15: 00000000ffffffa5
[  170.575274] FS:  00007fc6b7530700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[  170.575494] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  170.575665] CR2: 000000009fc1e520 CR3: 000000007c9c1000 CR4: 00000000000006f0
[  170.575870] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  170.576075] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  170.576276] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[  170.576507] Stack:
[  170.576599]  0000000000000010 0000000001893fbe ffff88009fc1e000 0000000000000050
[  170.576938]  000000009fc1e4c8 000000000000004f 00000000ffffffa5 ffffffff8112899f
[  170.576938]  ffff88003eb309d8 ffffffff81712d6d ffff88003e9bb980 ffff88009fc1e540
[  170.576938] Call Trace:
[  170.576938]  [<ffffffff8112899f>] ? check_poison_obj+0x1df/0x1f0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff81128a9d>] ? cache_alloc_debugcheck_after.isra.52+0xed/0x220
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff8112beb5>] ? kmem_cache_alloc+0xb5/0x1e0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff812edf2d>] ? acpi_ds_result_push+0x5d/0x12e
[  170.576938]  [<ffffffff812ed127>] ? acpi_ds_exec_end_op+0x28e/0x3d3
[  170.576938]  [<ffffffff812fd86a>] ? acpi_ps_parse_loop+0x79f/0x931
[  170.576938]  [<ffffffff812fdd6c>] ? acpi_ps_parse_aml+0x89/0x261
[  170.576938]  [<ffffffff812fe50c>] ? acpi_ps_execute_method+0x1be/0x266
[  170.576938]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[  170.576938]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[  170.576938]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[  170.576938]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[  170.576938]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[  170.576938]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[  170.576938]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[  170.576938]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[  170.576938]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[  170.576938]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[  170.576938]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[  170.576938]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[  170.576938] Code: cb 75 dc 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 8b 7f 0c 4c 89 e2 e8 02 fd ff ff 4c 89 e6 49 89 c5 48 89 ef e8 d4 fc ff ff <49> 8b 55 00 48 8b 30 48 c7 c7 8c 39 6f 81 31 c0 e8 3e 34 3b 00 

Other times, the problem happens on a slab object free:

[   52.313366] Offlined Pages 32768
[   52.800232] slab error in verify_redzone_free(): cache `Acpi-ParseExt': memory outside object was overwritten
[   52.801298] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12
[   52.802039] Call Trace:
[   52.802443]  [<ffffffff811280cb>] ? __slab_error.isra.46+0x1b/0x30
[   52.803199]  [<ffffffff811287b6>] ? cache_free_debugcheck+0x256/0x260
[   52.803940]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.804645]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.805321]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.806023]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.806762]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.807499]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.808183]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.808897]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.809659]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] ffff88008f809670: redzone 1:0x0, redzone 2:0x0.
[   52.810032] ------------[ cut here ]------------
[   52.810032] kernel BUG at mm/slab.c:3125!
[   52.810032] invalid opcode: 0000 [#1] SMP 
[   52.810032] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis tpm tpm_bios microcode parport_pc parport evdev processor thermal_sys psmouse i2c_piix4 serio_raw i2c_core button ext3 jbd mbcache sg sr_mod cdrom virtio_net ata_generic virtio_blk virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[   52.810032] CPU 0 
[   52.810032] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[   52.810032] RIP: 0010:[<ffffffff81128733>]  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032] RSP: 0018:ffff88003eaf3bc0  EFLAGS: 00010093
[   52.810032] RAX: 00000000017eac3c RBX: ffff88003e9bb700 RCX: 0000000002aaaaab
[   52.810032] RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000060
[   52.810032] RBP: ffff88008f809670 R08: 09f911029d74e35b R09: 0000000000000000
[   52.810032] R10: 00000000000001d3 R11: 0000000000000002 R12: ffff88008f809000
[   52.810032] R13: ffffffff812e1b0e R14: 0000000000000000 R15: 0000000000010c00
[   52.810032] FS:  00007f63fc263700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[   52.810032] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   52.810032] CR2: 00007fff8d895b78 CR3: 000000007c866000 CR4: 00000000000006f0
[   52.810032] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   52.810032] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   52.810032] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[   52.810032] Stack:
[   52.810032]  ffff88003e9bb980 ffff88008f809670 ffff880037ba8e18 ffff88008f809678
[   52.810032]  ffff88003e9bb700 0000000000000282 ffff88003e9bf270 ffffffff812e1b0e
[   52.810032]  0000000000000001 ffffffff81128fe3 ffff88003e80f5e8 ffff88003eb31748
[   52.810032] Call Trace:
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.810032]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.810032]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.810032]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.810032]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.810032]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] Code: 89 ea 49 89 38 8b 73 14 8b 7b 0c e8 18 f6 ff ff 49 b8 5b e3 74 9d 02 11 f9 09 4c 89 00 44 8b 7b 14 44 89 f8 e9 fa fe ff ff 0f 0b <0f> 0b 48 8b 40 30 e9 d9 fe ff ff e8 c6 43 3b 00 0f 0b 48 8b 40 
[   52.810032] RIP  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032]  RSP <ffff88003eaf3bc0>
[   52.810032] ---[ end trace c699c8cecd5870a3 ]---


And other times, I see a filesystem related slab corruption when doing the eject.
Here I have also seen a bad rss-counter state message. 

[  232.114232] BUG: Bad rss-counter state mm:ffff88007d9c1f80 idx:0 val:1
[  232.115214] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  232.115807] IP: [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.116186] PGD 7cdec067 PUD 7c946067 PMD 0 
[  232.116627] Oops: 0000 [#3] SMP 
[  232.116990] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor thermal_sys button ext3 jbd mbcache virtio_net sg sr_mod cdrom virtio_blk ata_generic virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[  232.120013] CPU 2 
[  232.120013] Pid: 880, comm: dhclient Tainted: G      D      3.6.0-rc7-guest #1 Bochs Bochs
[  232.120013] RIP: 0010:[<ffffffffa00cfce3>]  [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.120013] RSP: 0018:ffff88007cd6fab8  EFLAGS: 00010246
[  232.120013] RAX: ffff88003e513f50 RBX: ffff88003e513f50 RCX: 0000000000000000
[  232.120013] RDX: 0000000000000000 RSI: ffff88003e513f50 RDI: ffff880097800000
[  232.120013] RBP: ffff88003e513f50 R08: 000000003e513f01 R09: 0000000180240024
[  232.120013] R10: ffff88003e513f50 R11: 00000000000198e0 R12: 0000000000000000
[  232.120013] R13: ffffffffa00eb437 R14: ffff880097800000 R15: 000000000000027a
[  232.120013] FS:  00007f082638d700(0000) GS:ffff88003ec80000(0000) knlGS:0000000000000000
[  232.120013] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  232.120013] CR2: 0000000000000000 CR3: 000000007c94c000 CR4: 00000000000006e0
[  232.120013] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  232.120013] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  232.120013] Process dhclient (pid: 880, threadinfo ffff88007cd6e000, task ffff88007ca46800)
[  232.120013] Stack:
[  232.120013]  ffff88007dc205b0 ffffffff8116645f ffff88007dc205b0 ffff88007dc205b0
[  232.120013]  ffff88007cf58800 0000000000000000 000000000000000e 0000000000000000
[  232.120013]  000000000000027a ffffffff8112b934 0000005000000003 0000000000000fff
[  232.120013] Call Trace:
[  232.120013]  [<ffffffff8116645f>] ? __find_get_block+0x7f/0x200
[  232.120013]  [<ffffffff8112b934>] ? kmem_cache_alloc+0xe4/0x140
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffffa00d0279>] ? journal_get_write_access+0x29/0x50 [jbd]
[  232.120013]  [<ffffffffa00eaeef>] ? __ext3_get_inode_loc+0xcf/0x360 [ext3]
[  232.120013]  [<ffffffffa0101317>] ? __ext3_journal_get_write_access+0x27/0x60 [ext3]
[  232.120013]  [<ffffffffa00eb213>] ? ext3_reserve_inode_write+0x73/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb27b>] ? ext3_mark_inode_dirty+0x3b/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffff8115ded6>] ? __mark_inode_dirty+0x36/0x230
[  232.120013]  [<ffffffff811504a1>] ? update_time+0x71/0xb0
[  232.120013]  [<ffffffff811536c9>] ? mnt_clone_write+0x9/0x20
[  232.120013]  [<ffffffff81150581>] ? file_update_time+0xa1/0xf0
[  232.120013]  [<ffffffff8103385c>] ? ptep_set_access_flags+0x6c/0x70
[  232.120013]  [<ffffffff810e3f30>] ? __generic_file_aio_write+0x1a0/0x3c0
[  232.120013]  [<ffffffff811396fb>] ? __sb_start_write+0x6b/0x130
[  232.120013]  [<ffffffff810e41ce>] ? generic_file_aio_write+0x7e/0x100
[  232.120013]  [<ffffffff81137484>] ? do_sync_write+0x94/0xd0
[  232.120013]  [<ffffffff81137caa>] ? vfs_write+0xaa/0x160
[  232.120013]  [<ffffffff81137f87>] ? sys_write+0x47/0x90
[  232.120013]  [<ffffffff814e5765>] ? async_page_fault+0x25/0x30
[  232.120013]  [<ffffffff814eca79>] ? system_call_fastpath+0x16/0x1b
[  232.120013] Code: 54 24 2c f6 47 14 04 74 1f 41 bc e2 ff ff ff 48 81 c4 98 00 00 00 44 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 4c 8b 27 <4d> 8b 3c 24 41 f6 07 02 75 d4 65 48 8b 04 25 80 b9 00 00 48 89 

Is this a known issue? If yes, can you point me to any relevant patches?

When I do an SCI(hardware) eject, I have not seen corruptions. The acpi driver is
evaluating fewer objects in this path I think, but I don't see why corruption can't
happen here as well.

I have seen similar problems with CONFIG_SLUB (I did not have debug_options
there but I can also provide those if helpful)

[1] https://lkml.org/lkml/2012/9/6/635
[2] https://lkml.org/lkml/2012/9/11/542
[3] https://lkml.org/lkml/2012/9/20/37
[4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691

thanks,

- Vasilis

Re: [RFC v9 PATCH 00/21] memory-hotplug: hot-remove physical memory

From: Wen Congyang <hidden>
Date: 2012-10-09 08:06:08

At 09/27/2012 12:46 AM, Vasilis Liaskovitis Wrote:
Hi,

I am testing 3.6.0-rc7 with this v9 patchset plus more recent fixes [1],[2],[3]
Running in a guest (qemu+seabios from [4]). 
CONFIG_SLAB=y
CONFIG_DEBUG_SLAB=y

After succesfull hot-add and online, I am doing a hot-remove with "echo 1 > /sys/bus/acpi/devices/PNP/eject"
When I do the OSPM-eject, I often get slab corruption in "acpi-state" cache, or in other caches
The following patch can fix this problem:
https://lkml.org/lkml/2012/7/12/186

Thanks
Wen Congyang
[  170.566995] Slab corruption (Not tainted): Acpi-State start=ffff88009fc1e548, len=80
[  170.567265] Redzone: 0x0/0x0.
[  170.567399] Last user: [<          (null)>](0x0)
[  170.567667] 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568078] 010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568487] 020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.568894] 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569302] 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[  170.569712] Prev obj: start=000000009fc1e4d0, len=80
[  170.569869] BUG: unable to handle kernel paging request at 000000009fc1e520
[  170.570171] IP: [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.570397] PGD 7cf37067 PUD 0 
[  170.570619] Oops: 0000 [#1] SMP 
[  170.570843] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis microcode tpm tpm_bios psmouse parport_pc serio_raw evdev parport i2c_piix4 processor thermal_sys i2c_core button ext3 jbd mbcache sg sr_mod cdrom ata_generic virtio_net virtio_blk ata_piix libata scsi_mod virtio_pci virtio_ring virtio
[  170.573474] CPU 0 
[  170.573568] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[  170.573830] RIP: 0010:[<ffffffff8112803c>]  [<ffffffff8112803c>] print_objinfo+0x9c/0x110
[  170.574106] RSP: 0018:ffff88003eaf3a70  EFLAGS: 00010202
[  170.574268] RAX: 000000009fc1e4c8 RBX: 0000000000000002 RCX: 00000000000024b8
[  170.574468] RDX: 000000009fc1e4c8 RSI: 000000009fc1e4c8 RDI: ffff88003e9bb980
[  170.574668] RBP: ffff88003e9bb980 R08: ffff880037964078 R09: 0000000000000000
[  170.574870] R10: 000000000000021e R11: 0000000000000002 R12: 000000009fc1e4c8
[  170.575070] R13: 000000009fc1e520 R14: 000000000000004f R15: 00000000ffffffa5
[  170.575274] FS:  00007fc6b7530700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[  170.575494] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  170.575665] CR2: 000000009fc1e520 CR3: 000000007c9c1000 CR4: 00000000000006f0
[  170.575870] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  170.576075] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  170.576276] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[  170.576507] Stack:
[  170.576599]  0000000000000010 0000000001893fbe ffff88009fc1e000 0000000000000050
[  170.576938]  000000009fc1e4c8 000000000000004f 00000000ffffffa5 ffffffff8112899f
[  170.576938]  ffff88003eb309d8 ffffffff81712d6d ffff88003e9bb980 ffff88009fc1e540
[  170.576938] Call Trace:
[  170.576938]  [<ffffffff8112899f>] ? check_poison_obj+0x1df/0x1f0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff81128a9d>] ? cache_alloc_debugcheck_after.isra.52+0xed/0x220
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff8112beb5>] ? kmem_cache_alloc+0xb5/0x1e0
[  170.576938]  [<ffffffff813047d0>] ? acpi_ut_create_generic_state+0x2f/0x4c
[  170.576938]  [<ffffffff812edf2d>] ? acpi_ds_result_push+0x5d/0x12e
[  170.576938]  [<ffffffff812ed127>] ? acpi_ds_exec_end_op+0x28e/0x3d3
[  170.576938]  [<ffffffff812fd86a>] ? acpi_ps_parse_loop+0x79f/0x931
[  170.576938]  [<ffffffff812fdd6c>] ? acpi_ps_parse_aml+0x89/0x261
[  170.576938]  [<ffffffff812fe50c>] ? acpi_ps_execute_method+0x1be/0x266
[  170.576938]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[  170.576938]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[  170.576938]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[  170.576938]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[  170.576938]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[  170.576938]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[  170.576938]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[  170.576938]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[  170.576938]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[  170.576938]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[  170.576938]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[  170.576938]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[  170.576938] Code: cb 75 dc 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 8b 7f 0c 4c 89 e2 e8 02 fd ff ff 4c 89 e6 49 89 c5 48 89 ef e8 d4 fc ff ff <49> 8b 55 00 48 8b 30 48 c7 c7 8c 39 6f 81 31 c0 e8 3e 34 3b 00 

Other times, the problem happens on a slab object free:

[   52.313366] Offlined Pages 32768
[   52.800232] slab error in verify_redzone_free(): cache `Acpi-ParseExt': memory outside object was overwritten
[   52.801298] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12
[   52.802039] Call Trace:
[   52.802443]  [<ffffffff811280cb>] ? __slab_error.isra.46+0x1b/0x30
[   52.803199]  [<ffffffff811287b6>] ? cache_free_debugcheck+0x256/0x260
[   52.803940]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.804645]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.805321]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.806023]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.806762]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.807499]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.808183]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.808897]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.809659]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] ffff88008f809670: redzone 1:0x0, redzone 2:0x0.
[   52.810032] ------------[ cut here ]------------
[   52.810032] kernel BUG at mm/slab.c:3125!
[   52.810032] invalid opcode: 0000 [#1] SMP 
[   52.810032] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm tpm_tis tpm tpm_bios microcode parport_pc parport evdev processor thermal_sys psmouse i2c_piix4 serio_raw i2c_core button ext3 jbd mbcache sg sr_mod cdrom virtio_net ata_generic virtio_blk virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[   52.810032] CPU 0 
[   52.810032] Pid: 29, comm: kworker/0:1 Not tainted 3.6.0-rc7-guest #12 Bochs Bochs
[   52.810032] RIP: 0010:[<ffffffff81128733>]  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032] RSP: 0018:ffff88003eaf3bc0  EFLAGS: 00010093
[   52.810032] RAX: 00000000017eac3c RBX: ffff88003e9bb700 RCX: 0000000002aaaaab
[   52.810032] RDX: 0000000000000000 RSI: 0000000000010000 RDI: 0000000000000060
[   52.810032] RBP: ffff88008f809670 R08: 09f911029d74e35b R09: 0000000000000000
[   52.810032] R10: 00000000000001d3 R11: 0000000000000002 R12: ffff88008f809000
[   52.810032] R13: ffffffff812e1b0e R14: 0000000000000000 R15: 0000000000010c00
[   52.810032] FS:  00007f63fc263700(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[   52.810032] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   52.810032] CR2: 00007fff8d895b78 CR3: 000000007c866000 CR4: 00000000000006f0
[   52.810032] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   52.810032] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   52.810032] Process kworker/0:1 (pid: 29, threadinfo ffff88003eaf2000, task ffff88003ea941c0)
[   52.810032] Stack:
[   52.810032]  ffff88003e9bb980 ffff88008f809670 ffff880037ba8e18 ffff88008f809678
[   52.810032]  ffff88003e9bb700 0000000000000282 ffff88003e9bf270 ffffffff812e1b0e
[   52.810032]  0000000000000001 ffffffff81128fe3 ffff88003e80f5e8 ffff88003eb31748
[   52.810032] Call Trace:
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff81128fe3>] ? kmem_cache_free+0x63/0x260
[   52.810032]  [<ffffffff812e1b0e>] ? acpi_os_release_object+0x7/0xc
[   52.810032]  [<ffffffff812fe298>] ? acpi_ps_delete_parse_tree+0x34/0x58
[   52.810032]  [<ffffffff812fe517>] ? acpi_ps_execute_method+0x1c9/0x266
[   52.810032]  [<ffffffff812f91f7>] ? acpi_ns_evaluate+0xd3/0x19a
[   52.810032]  [<ffffffff812fb93e>] ? acpi_evaluate_object+0xf3/0x1f4
[   52.810032]  [<ffffffff812e1104>] ? acpi_os_wait_events_complete+0x1b/0x1b
[   52.810032]  [<ffffffff812e4782>] ? acpi_bus_hot_remove_device+0xeb/0x123
[   52.810032]  [<ffffffff812e1121>] ? acpi_os_execute_deferred+0x1d/0x29
[   52.810032]  [<ffffffff81058ec5>] ? process_one_work+0x125/0x560
[   52.810032]  [<ffffffff81059e7a>] ? worker_thread+0x16a/0x4e0
[   52.810032]  [<ffffffff81059d10>] ? manage_workers+0x310/0x310
[   52.810032]  [<ffffffff8105e6c5>] ? kthread+0x85/0x90
[   52.810032]  [<ffffffff814eb2c4>] ? kernel_thread_helper+0x4/0x10
[   52.810032]  [<ffffffff8105e640>] ? flush_kthread_worker+0xa0/0xa0
[   52.810032]  [<ffffffff814eb2c0>] ? gs_change+0x13/0x13
[   52.810032] Code: 89 ea 49 89 38 8b 73 14 8b 7b 0c e8 18 f6 ff ff 49 b8 5b e3 74 9d 02 11 f9 09 4c 89 00 44 8b 7b 14 44 89 f8 e9 fa fe ff ff 0f 0b <0f> 0b 48 8b 40 30 e9 d9 fe ff ff e8 c6 43 3b 00 0f 0b 48 8b 40 
[   52.810032] RIP  [<ffffffff81128733>] cache_free_debugcheck+0x1d3/0x260
[   52.810032]  RSP <ffff88003eaf3bc0>
[   52.810032] ---[ end trace c699c8cecd5870a3 ]---


And other times, I see a filesystem related slab corruption when doing the eject.
Here I have also seen a bad rss-counter state message. 

[  232.114232] BUG: Bad rss-counter state mm:ffff88007d9c1f80 idx:0 val:1
[  232.115214] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  232.115807] IP: [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.116186] PGD 7cdec067 PUD 7c946067 PMD 0 
[  232.116627] Oops: 0000 [#3] SMP 
[  232.116990] Modules linked in: netconsole acpiphp pci_hotplug acpi_memhotplug loop kvm_amd kvm microcode tpm_tis tpm tpm_bios evdev psmouse serio_raw i2c_piix4 i2c_core parport_pc parport processor thermal_sys button ext3 jbd mbcache virtio_net sg sr_mod cdrom virtio_blk ata_generic virtio_pci virtio_ring virtio ata_piix libata scsi_mod
[  232.120013] CPU 2 
[  232.120013] Pid: 880, comm: dhclient Tainted: G      D      3.6.0-rc7-guest #1 Bochs Bochs
[  232.120013] RIP: 0010:[<ffffffffa00cfce3>]  [<ffffffffa00cfce3>] do_get_write_access+0x43/0x480 [jbd]
[  232.120013] RSP: 0018:ffff88007cd6fab8  EFLAGS: 00010246
[  232.120013] RAX: ffff88003e513f50 RBX: ffff88003e513f50 RCX: 0000000000000000
[  232.120013] RDX: 0000000000000000 RSI: ffff88003e513f50 RDI: ffff880097800000
[  232.120013] RBP: ffff88003e513f50 R08: 000000003e513f01 R09: 0000000180240024
[  232.120013] R10: ffff88003e513f50 R11: 00000000000198e0 R12: 0000000000000000
[  232.120013] R13: ffffffffa00eb437 R14: ffff880097800000 R15: 000000000000027a
[  232.120013] FS:  00007f082638d700(0000) GS:ffff88003ec80000(0000) knlGS:0000000000000000
[  232.120013] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  232.120013] CR2: 0000000000000000 CR3: 000000007c94c000 CR4: 00000000000006e0
[  232.120013] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  232.120013] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  232.120013] Process dhclient (pid: 880, threadinfo ffff88007cd6e000, task ffff88007ca46800)
[  232.120013] Stack:
[  232.120013]  ffff88007dc205b0 ffffffff8116645f ffff88007dc205b0 ffff88007dc205b0
[  232.120013]  ffff88007cf58800 0000000000000000 000000000000000e 0000000000000000
[  232.120013]  000000000000027a ffffffff8112b934 0000005000000003 0000000000000fff
[  232.120013] Call Trace:
[  232.120013]  [<ffffffff8116645f>] ? __find_get_block+0x7f/0x200
[  232.120013]  [<ffffffff8112b934>] ? kmem_cache_alloc+0xe4/0x140
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffffa00d0279>] ? journal_get_write_access+0x29/0x50 [jbd]
[  232.120013]  [<ffffffffa00eaeef>] ? __ext3_get_inode_loc+0xcf/0x360 [ext3]
[  232.120013]  [<ffffffffa0101317>] ? __ext3_journal_get_write_access+0x27/0x60 [ext3]
[  232.120013]  [<ffffffffa00eb213>] ? ext3_reserve_inode_write+0x73/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb27b>] ? ext3_mark_inode_dirty+0x3b/0xa0 [ext3]
[  232.120013]  [<ffffffffa00eb437>] ? ext3_dirty_inode+0x57/0xb0 [ext3]
[  232.120013]  [<ffffffff8115ded6>] ? __mark_inode_dirty+0x36/0x230
[  232.120013]  [<ffffffff811504a1>] ? update_time+0x71/0xb0
[  232.120013]  [<ffffffff811536c9>] ? mnt_clone_write+0x9/0x20
[  232.120013]  [<ffffffff81150581>] ? file_update_time+0xa1/0xf0
[  232.120013]  [<ffffffff8103385c>] ? ptep_set_access_flags+0x6c/0x70
[  232.120013]  [<ffffffff810e3f30>] ? __generic_file_aio_write+0x1a0/0x3c0
[  232.120013]  [<ffffffff811396fb>] ? __sb_start_write+0x6b/0x130
[  232.120013]  [<ffffffff810e41ce>] ? generic_file_aio_write+0x7e/0x100
[  232.120013]  [<ffffffff81137484>] ? do_sync_write+0x94/0xd0
[  232.120013]  [<ffffffff81137caa>] ? vfs_write+0xaa/0x160
[  232.120013]  [<ffffffff81137f87>] ? sys_write+0x47/0x90
[  232.120013]  [<ffffffff814e5765>] ? async_page_fault+0x25/0x30
[  232.120013]  [<ffffffff814eca79>] ? system_call_fastpath+0x16/0x1b
[  232.120013] Code: 54 24 2c f6 47 14 04 74 1f 41 bc e2 ff ff ff 48 81 c4 98 00 00 00 44 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 4c 8b 27 <4d> 8b 3c 24 41 f6 07 02 75 d4 65 48 8b 04 25 80 b9 00 00 48 89 

Is this a known issue? If yes, can you point me to any relevant patches?

When I do an SCI(hardware) eject, I have not seen corruptions. The acpi driver is
evaluating fewer objects in this path I think, but I don't see why corruption can't
happen here as well.

I have seen similar problems with CONFIG_SLUB (I did not have debug_options
there but I can also provide those if helpful)

[1] https://lkml.org/lkml/2012/9/6/635
[2] https://lkml.org/lkml/2012/9/11/542
[3] https://lkml.org/lkml/2012/9/20/37
[4] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/98691

thanks,

- Vasilis
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help