From: "Michal Nazarewicz" <mina86@mina86.com>
To: Mel Gorman <mgorman@suse.de>,
Herbert van den Bergh <herbert.van.den.bergh@oracle.com>
Cc: linux-mm@kvack.org
Subject: Re: [BUG] 3.2.2 crash in isolate_migratepages
Date: Mon, 30 Jan 2012 19:28:16 +0100 [thread overview]
Message-ID: <op.v8wtleuf3l0zgt@mpn-glaptop> (raw)
In-Reply-To: <4F26DE75.5050409@oracle.com>
> On 1/30/12 1:09 AM, Mel Gorman wrote:
>> The migrate_pfn is just below a memory hole and the free scanner is
>> beyond the hole. When isolate_migratepages started, it scans from
>> migrate_pfn to migrate_pfn+pageblock_nr_pages which is now in a memory
>> hole. It checks pfn_valid() on the first PFN but then scans into the
>> hole where there are not necessarily valid struct pages.
>>
>> This patch ensures that isolate_migratepages calls pfn_valid when
>> necessary.
>>
>> Signed-off-by: Mel Gorman <mgorman@suse.de>
If anyone cares, this looks good to me, so:
Acked-by: Michal Nazarewicz <mina86@mina86.com>
>> ---
>> mm/compaction.c | 13 +++++++++++++
>> 1 files changed, 13 insertions(+), 0 deletions(-)
>>
>> diff --git a/mm/compaction.c b/mm/compaction.c
>> index 899d956..edc1e26 100644
>> --- a/mm/compaction.c
>> +++ b/mm/compaction.c
>> @@ -313,6 +313,19 @@ static isolate_migrate_t isolate_migratepages(struct zone *zone,
>> } else if (!locked)
>> spin_lock_irq(&zone->lru_lock);
>>
>> + /*
>> + * migrate_pfn does not necessarily start aligned to a
>> + * pageblock. Ensure that pfn_valid is called when moving
>> + * into a new MAX_ORDER_NR_PAGES range in case of large
>> + * memory holes within the zone
>> + */
>> + if ((low_pfn & (MAX_ORDER_NR_PAGES - 1)) == 0) {
>> + if (!pfn_valid(low_pfn)) {
>> + low_pfn += MAX_ORDER_NR_PAGES - 1;
>> + continue;
>> + }
>> + }
>> +
>> if (!pfn_valid_within(low_pfn))
>> continue;
>> nr_scanned++;
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-01-30 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 21:43 Herbert van den Bergh
2012-01-30 9:09 ` Mel Gorman
2012-01-30 18:16 ` Herbert van den Bergh
2012-01-30 18:28 ` Michal Nazarewicz [this message]
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=op.v8wtleuf3l0zgt@mpn-glaptop \
--to=mina86@mina86.com \
--cc=herbert.van.den.bergh@oracle.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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