The patch titled debug-pagealloc: cannot depend on hibernation has been removed from the -mm tree. Its filename was generic-debug-pagealloc-cannot-depend-on-hibernation.patch This patch was dropped because it was folded into generic-debug-pagealloc-v4.patch The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: debug-pagealloc: cannot depend on hibernation From: Akinobu Mita <akinobu.mita@xxxxxxxxx> The generic debug-pagealloc generates wrong messages for the page corruption after hibernation. Because the free pages are not saved to the suspend image. Signed-off-by: Akinobu Mita <akinobu.mita@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/Kconfig.debug | 5 +++++ 1 file changed, 5 insertions(+) diff -puN mm/Kconfig.debug~generic-debug-pagealloc-cannot-depend-on-hibernation mm/Kconfig.debug --- a/mm/Kconfig.debug~generic-debug-pagealloc-cannot-depend-on-hibernation +++ a/mm/Kconfig.debug @@ -4,9 +4,14 @@ config WANT_PAGE_DEBUG_FLAGS config PAGE_POISONING bool "Debug page memory allocations" depends on DEBUG_KERNEL && !ARCH_SUPPORTS_DEBUG_PAGEALLOC + depends on !HIBERNATION select DEBUG_PAGEALLOC select WANT_PAGE_DEBUG_FLAGS help Fill the pages with poison patterns after free_pages() and verify the patterns before alloc_pages(). This results in a large slowdown, but helps to find certain types of memory corruptions. + + This option cannot enalbe with hibernation. Otherwise, it will get + wrong messages for memory corruption because the free pages are not + saved to the suspend image. _ Patches currently in -mm which might be from akinobu.mita@xxxxxxxxx are origin.patch generic-debug-pagealloc-v4.patch generic-debug-pagealloc-cannot-depend-on-hibernation.patch introduce-debug_kmap_atomic.patch use-debug_kmap_atomic.patch loop-add-ioctl-to-resize-a-loop-device.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html