On 20 May 2015 at 1:46, Rafael J. Wysocki wrote: > swsusp_free() is *the* function that, well, frees all the pages allocated > by the hibernate core, so how isn't the free pages bitmap valid when it is > called? > > Why don't you add the clearing in there, right at the spot when the pages > are actually freed? actually swsusp_free uses __free_page which in turn will go through the page sanitization logic so there's no need for extra sanitization. that said ... > Moreover, why is the resume code path the only one where freed pages need to > be sanitized? ... i had a bug report before (http://marc.info/?l=linux-pm&m=132871433416256) which is why i asked Anisse to figure this out before upstreaming the feature. i've also asked him already to explain why his approach is the proper fix for the problem (which should include the description of the root cause as a start) but he hasn't answered that yet. anyway, the big question is how there can be free memory pages after resume which are not sanitized. now i have no idea about the hibernation logic but i assume that it doesn't save/restore free pages so the question is how the kernel gets to learn about these free pages during resume and whether there's a path where __free_page() or some other wrapper around free_pages_prepare() doesn't get called at all. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>