From: "PaX Team" <pageexec@freemail.hu> To: Anisse Astier <anisse@astier.eu>, "Rafael J. Wysocki" <rjw@rjwysocki.net> Cc: Andrew Morton <akpm@linux-foundation.org>, Mel Gorman <mgorman@suse.de>, "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>, David Rientjes <rientjes@google.com>, Alan Cox <gnomes@lxorguk.ukuu.org.uk>, Linus Torvalds <torvalds@linux-foundation.org>, Peter Zijlstra <peterz@infradead.org>, Brad Spengler <spender@grsecurity.net>, Kees Cook <keescook@chromium.org>, Andi Kleen <andi@firstfloor.org>, Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>, linux-mm@kvack.org, Linux PM list <linux-pm@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES Date: Wed, 20 May 2015 13:45:43 +0200 [thread overview] Message-ID: <555C73E7.23237.269170A5@pageexec.freemail.hu> (raw) In-Reply-To: <1526358.9aMpXL2Hv2@vostro.rjw.lan> 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.
WARNING: multiple messages have this Message-ID (diff)
From: "PaX Team" <pageexec@freemail.hu> To: Anisse Astier <anisse@astier.eu>, "Rafael J. Wysocki" <rjw@rjwysocki.net> Cc: Andrew Morton <akpm@linux-foundation.org>, Mel Gorman <mgorman@suse.de>, "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>, David Rientjes <rientjes@google.com>, Alan Cox <gnomes@lxorguk.ukuu.org.uk>, Linus Torvalds <torvalds@linux-foundation.org>, Peter Zijlstra <peterz@infradead.org>, Brad Spengler <spender@grsecurity.net>, Kees Cook <keescook@chromium.org>, Andi Kleen <andi@firstfloor.org>, Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>, linux-mm@kvack.org, Linux PM list <linux-pm@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES Date: Wed, 20 May 2015 13:45:43 +0200 [thread overview] Message-ID: <555C73E7.23237.269170A5@pageexec.freemail.hu> (raw) In-Reply-To: <1526358.9aMpXL2Hv2@vostro.rjw.lan> 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@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>
next prev parent reply other threads:[~2015-05-20 11:48 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-14 14:19 [PATCH v4 0/3] Sanitizing freed pages Anisse Astier 2015-05-14 14:19 ` Anisse Astier 2015-05-14 14:19 ` Anisse Astier 2015-05-14 14:19 ` [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES Anisse Astier 2015-05-14 14:19 ` Anisse Astier 2015-05-16 0:28 ` Rafael J. Wysocki 2015-05-16 0:28 ` Rafael J. Wysocki 2015-05-18 10:23 ` Anisse Astier 2015-05-18 10:23 ` Anisse Astier 2015-05-19 23:46 ` Rafael J. Wysocki 2015-05-19 23:46 ` Rafael J. Wysocki 2015-05-20 11:45 ` PaX Team [this message] 2015-05-20 11:45 ` PaX Team 2015-05-20 12:07 ` Anisse Astier 2015-05-20 12:07 ` Anisse Astier 2015-05-21 1:11 ` Rafael J. Wysocki 2015-05-21 1:11 ` Rafael J. Wysocki 2015-05-20 11:57 ` Anisse Astier 2015-05-20 11:57 ` Anisse Astier 2015-05-14 14:19 ` [PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages Anisse Astier 2015-05-14 14:19 ` Anisse Astier 2015-05-18 11:21 ` Pavel Machek 2015-05-18 11:21 ` Pavel Machek 2015-05-18 12:41 ` Anisse Astier 2015-05-18 12:41 ` Anisse Astier 2015-05-18 13:02 ` Pavel Machek 2015-05-18 13:02 ` Pavel Machek 2015-05-18 13:04 ` Anisse Astier 2015-05-18 13:04 ` Anisse Astier 2015-05-19 1:58 ` yalin wang 2015-05-20 12:27 ` Anisse Astier 2015-05-20 12:27 ` Anisse Astier 2015-05-14 14:19 ` [PATCH v4 3/3] mm: Add debug code for SANITIZE_FREED_PAGES Anisse Astier 2015-05-14 14:19 ` Anisse Astier 2015-05-19 12:46 ` [PATCH v4 0/3] Sanitizing freed pages Mel Gorman 2015-05-19 12:46 ` Mel Gorman 2015-05-19 13:35 ` One Thousand Gnomes 2015-05-19 13:35 ` One Thousand Gnomes 2015-05-19 13:56 ` Mel Gorman 2015-05-19 13:56 ` Mel Gorman 2015-05-19 20:59 ` PaX Team 2015-05-19 20:59 ` PaX Team 2015-05-20 12:24 ` Anisse Astier 2015-05-20 12:24 ` Anisse Astier
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=555C73E7.23237.269170A5@pageexec.freemail.hu \ --to=pageexec@freemail.hu \ --cc=akpm@linux-foundation.org \ --cc=andi@firstfloor.org \ --cc=anisse@astier.eu \ --cc=gnomes@lxorguk.ukuu.org.uk \ --cc=keescook@chromium.org \ --cc=kirill.shutemov@linux.intel.com \ --cc=len.brown@intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-pm@vger.kernel.org \ --cc=mgorman@suse.de \ --cc=pavel@ucw.cz \ --cc=peterz@infradead.org \ --cc=rientjes@google.com \ --cc=rjw@rjwysocki.net \ --cc=spender@grsecurity.net \ --cc=torvalds@linux-foundation.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.