From: osalvador@suse.de
To: akpm@linux-foundation.org
Cc: mhocko@suse.com, david@redhat.com, pasha.tatashin@soleen.com,
dan.j.williams@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, owner-linux-mm@kvack.org
Subject: Re: [PATCH] mm, memory_hotplug: Don't bail out in do_migrate_range prematurely
Date: Tue, 11 Dec 2018 09:57:11 +0100 [thread overview]
Message-ID: <01021c8571af27995acbaaca7a1a68f0@suse.de> (raw)
In-Reply-To: <20181211085042.2696-1-osalvador@suse.de>
On 2018-12-11 09:50, Oscar Salvador wrote:
> - } else {
> - pr_warn("failed to isolate pfn %lx\n", pfn);
> - dump_page(page, "isolation failed");
> - put_page(page);
> - /* Because we don't have big zone->lock. we should
> - check this again here. */
> - if (page_count(page)) {
> - not_managed++;
> - ret = -EBUSY;
> - break;
I forgot that here we should at least leave the put_page().
But leave also the dump_page() and the pr_warn().
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -1394,6 +1394,10 @@ do_migrate_range(unsigned long start_pfn,
unsigned long end_pfn)
inc_node_page_state(page,
NR_ISOLATED_ANON +
page_is_file_cache(page));
+ } else {
+ pr_warn("failed to isolate pfn %lx\n", pfn);
+ dump_page(page, "isolation failed");
+ put_page(page);
}
}
if (!list_empty(&source)) {
next prev parent reply other threads:[~2018-12-11 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 8:50 Oscar Salvador
2018-12-11 8:57 ` osalvador [this message]
2018-12-11 9:37 ` David Hildenbrand
2018-12-11 9:35 ` David Hildenbrand
2018-12-11 10:20 ` Michal Hocko
2018-12-11 10:35 ` David Hildenbrand
2018-12-11 10:18 ` Michal Hocko
2018-12-11 12:22 ` osalvador
2018-12-11 12:52 ` 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=01021c8571af27995acbaaca7a1a68f0@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=owner-linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
/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