search for: pg_hwpoison

...r 2016 14:26:30 +0900 Subject: [PATCH] mm/hwpoison: fix wrong num_poisoned_pages account Currently, migartion code increses num_poisoned_pages on *failed* migration page as well as successfully migrated one at the trial of memory-failture. It will make the stat wrong. As well, it marks the page as PG_HWPoison even if the migration trial failed. It would make we cannot recover the corrupted page using memory-failure facility. This patches fixes it. Cc: stable at vger.kernel.org Signed-off-by: Minchan Kim <minchan at kernel.org> --- mm/migrate.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 de...

...r 2016 14:26:30 +0900 Subject: [PATCH] mm/hwpoison: fix wrong num_poisoned_pages account Currently, migartion code increses num_poisoned_pages on *failed* migration page as well as successfully migrated one at the trial of memory-failture. It will make the stat wrong. As well, it marks the page as PG_HWPoison even if the migration trial failed. It would make we cannot recover the corrupted page using memory-failure facility. This patches fixes it. Cc: stable at vger.kernel.org Signed-off-by: Minchan Kim <minchan at kernel.org> --- mm/migrate.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 de...

@Andrew, @Mst, I suggest the whole series (including the virtio-mem change) goes via the -mm tree. Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to ZONE_MOVABLE and will never consider such memory blocks when unplugging memory. This might be surprising

For 5.10. Patch #1-#4,#6 have RBs or ACKs, patch #5 is virtio-mem stuff maintained by me. This should go via the -mm tree. --- When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather unclear, which is why we special-cased ZONE_MOVABLE such that partially plugged blocks would never end up in ZONE_MOVABLE. Now that the semantics are much clearer (and are documented in patch #6),

For 5.10. Patch #1-#4,#6 have RBs or ACKs, patch #5 is virtio-mem stuff maintained by me. This should go via the -mm tree. --- When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather unclear, which is why we special-cased ZONE_MOVABLE such that partially plugged blocks would never end up in ZONE_MOVABLE. Now that the semantics are much clearer (and are documented in patch #6),

@Andrew can we give this a churn and consider it for v5.9 in case there are no more comments? Patch #1-#4,#6 have RBss or ACKs, patch #5 is virtio-mem stuff maintained by me (and MST is aware). --- When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather unclear, which is why we special-cased ZONE_MOVABLE such that partially plugged blocks would never end up in ZONE_MOVABLE. Now

@Andrew can we give this a churn and consider it for v5.9 in case there are no more comments? Patch #1-#4,#6 have RBss or ACKs, patch #5 is virtio-mem stuff maintained by me (and MST is aware). --- When introducing virtio-mem, the semantics of ZONE_MOVABLE were rather unclear, which is why we special-cased ZONE_MOVABLE such that partially plugged blocks would never end up in ZONE_MOVABLE. Now

@Andrew can we give this a churn and consider it for v5.9 in case there are no more comments? Patch #1-#4 have RB's, patch #5 is virtio-mem stuff maintained by me, patch #6 is just a doc update. --- Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to

@Andrew can we give this a churn and consider it for v5.9 in case there are no more comments? Patch #1-#4 have RB's, patch #5 is virtio-mem stuff maintained by me, patch #6 is just a doc update. --- Currently, virtio-mem does not really support ZONE_MOVABLE. While it allows to online fully plugged memory blocks to ZONE_MOVABLE, it does not allow to online partially-plugged memory blocks to