From: Michal Hocko <mhocko@kernel.org>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
x86@kernel.org, kasan-dev@googlegroups.com,
borntraeger@de.ibm.com, heiko.carstens@de.ibm.com,
davem@davemloft.net, willy@infradead.org,
ard.biesheuvel@linaro.org, will.deacon@arm.com,
catalin.marinas@arm.com, sam@ravnborg.org,
Mel Gorman <mgorman@suse.de>
Subject: Re: [v6 05/15] mm: don't accessed uninitialized struct pages
Date: Tue, 15 Aug 2017 11:33:07 +0200 [thread overview]
Message-ID: <20170815093306.GC29067@dhcp22.suse.cz> (raw)
In-Reply-To: <1502138329-123460-6-git-send-email-pasha.tatashin@oracle.com>
[CC Mel - the original patch was
http://lkml.kernel.org/r/1502138329-123460-6-git-send-email-pasha.tatashin@oracle.com]
On Mon 07-08-17 16:38:39, Pavel Tatashin wrote:
> In deferred_init_memmap() where all deferred struct pages are initialized
> we have a check like this:
>
> if (page->flags) {
> VM_BUG_ON(page_zone(page) != zone);
> goto free_range;
> }
>
> This way we are checking if the current deferred page has already been
> initialized. It works, because memory for struct pages has been zeroed, and
> the only way flags are not zero if it went through __init_single_page()
> before. But, once we change the current behavior and won't zero the memory
> in memblock allocator, we cannot trust anything inside "struct page"es
> until they are initialized. This patch fixes this.
>
> This patch defines a new accessor memblock_get_reserved_pfn_range()
> which returns successive ranges of reserved PFNs. deferred_init_memmap()
> calls it to determine if a PFN and its struct page has already been
> initialized.
Maybe I am missing something but how can we see reserved ranges here
when for_each_mem_pfn_range iterates over memblock.memory?
The loop is rather complex but I am wondering whether the page->flags
check is needed at all. We shouldn't have duplicated memblocks covering
the same pfn ranges so we cannot initialize the same range multiple
times, right? Reserved ranges are excluded altogether so how exactly can
we see an initialized struct page? In other words, why this simply
doesn't work?
---
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 90e331e4c077..987a340a5bed 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -1524,11 +1524,6 @@ static int __init deferred_init_memmap(void *data)
cond_resched();
}
- if (page->flags) {
- VM_BUG_ON(page_zone(page) != zone);
- goto free_range;
- }
-
__init_single_page(page, pfn, zid, nid);
if (!free_base_page) {
free_base_page = page;
--
Michal Hocko
SUSE Labs
--
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:[~2017-08-15 9:33 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 20:38 [v6 00/15] complete deferred page initialization Pavel Tatashin
2017-08-07 20:38 ` [v6 01/15] x86/mm: reserve only exiting low pages Pavel Tatashin
2017-08-11 8:07 ` Michal Hocko
2017-08-11 15:24 ` Pasha Tatashin
2017-08-14 11:40 ` Michal Hocko
2017-08-14 13:30 ` Pasha Tatashin
2017-08-14 13:55 ` Michal Hocko
2017-08-17 15:37 ` Pasha Tatashin
2017-08-07 20:38 ` [v6 02/15] x86/mm: setting fields in deferred pages Pavel Tatashin
2017-08-11 9:02 ` Michal Hocko
2017-08-11 15:39 ` Pasha Tatashin
2017-08-14 11:43 ` Michal Hocko
2017-08-14 13:32 ` Pasha Tatashin
2017-08-07 20:38 ` [v6 03/15] sparc64/mm: " Pavel Tatashin
2017-08-07 20:38 ` [v6 04/15] mm: discard memblock data later Pavel Tatashin
2017-08-11 9:32 ` Michal Hocko
2017-08-11 9:50 ` Mel Gorman
2017-08-11 15:49 ` Pasha Tatashin
2017-08-11 16:04 ` Michal Hocko
2017-08-11 16:22 ` Pasha Tatashin
2017-08-14 11:36 ` Michal Hocko
2017-08-14 13:35 ` Pasha Tatashin
2017-08-11 19:00 ` Pasha Tatashin
2017-08-14 11:34 ` Michal Hocko
2017-08-14 13:39 ` Pasha Tatashin
2017-08-14 13:42 ` Michal Hocko
2017-08-07 20:38 ` [v6 05/15] mm: don't accessed uninitialized struct pages Pavel Tatashin
2017-08-11 9:37 ` Michal Hocko
2017-08-11 15:55 ` Pasha Tatashin
2017-08-14 11:47 ` Michal Hocko
2017-08-14 13:51 ` Pasha Tatashin
2017-08-17 15:28 ` Pasha Tatashin
2017-08-17 15:43 ` Michal Hocko
2017-08-15 9:33 ` Michal Hocko [this message]
2017-08-07 20:38 ` [v6 06/15] sparc64: simplify vmemmap_populate Pavel Tatashin
2017-08-07 20:38 ` [v6 07/15] mm: defining memblock_virt_alloc_try_nid_raw Pavel Tatashin
2017-08-11 12:39 ` Michal Hocko
2017-08-11 15:58 ` Pasha Tatashin
2017-08-11 16:06 ` Michal Hocko
2017-08-11 16:24 ` Pasha Tatashin
2017-08-07 20:38 ` [v6 08/15] mm: zero struct pages during initialization Pavel Tatashin
2017-08-11 12:50 ` Michal Hocko
2017-08-11 16:03 ` Pasha Tatashin
2017-08-07 20:38 ` [v6 09/15] sparc64: optimized struct page zeroing Pavel Tatashin
2017-08-11 12:53 ` Michal Hocko
2017-08-11 16:04 ` Pasha Tatashin
2017-08-07 20:38 ` [v6 10/15] x86/kasan: explicitly zero kasan shadow memory Pavel Tatashin
2017-08-07 20:38 ` [v6 11/15] arm64/kasan: " Pavel Tatashin
2017-08-08 9:07 ` Will Deacon
2017-08-08 11:49 ` Pasha Tatashin
2017-08-08 12:30 ` Will Deacon
2017-08-08 12:49 ` Pasha Tatashin
2017-08-08 13:15 ` David Laight
2017-08-08 13:30 ` Pasha Tatashin
2017-08-07 20:38 ` [v6 12/15] mm: explicitly zero pagetable memory Pavel Tatashin
2017-08-07 20:38 ` [v6 13/15] mm: stop zeroing memory during allocation in vmemmap Pavel Tatashin
2017-08-11 13:04 ` Michal Hocko
2017-08-11 16:11 ` Pasha Tatashin
2017-08-07 20:38 ` [v6 14/15] mm: optimize early system hash allocations Pavel Tatashin
2017-08-11 13:05 ` Michal Hocko
2017-08-11 16:13 ` Pasha Tatashin
2017-08-07 20:38 ` [v6 15/15] mm: debug for raw alloctor Pavel Tatashin
2017-08-11 13:08 ` Michal Hocko
2017-08-11 16:18 ` Pasha Tatashin
2017-08-14 11:50 ` Michal Hocko
2017-08-14 14:01 ` Pasha Tatashin
2017-08-15 9:36 ` Michal Hocko
2017-08-11 7:58 ` [v6 00/15] complete deferred page initialization Michal Hocko
2017-08-11 15:13 ` Pasha Tatashin
2017-08-11 15:22 ` Michal Hocko
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=20170815093306.GC29067@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mgorman@suse.de \
--cc=pasha.tatashin@oracle.com \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=willy@infradead.org \
--cc=x86@kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox