linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Mel Gorman <mgorman@suse.de>, Tejun Heo <tj@kernel.org>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
	Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] mm, memory_hotplug: do not back off draining pcp free pages from kworker context
Date: Mon, 28 Aug 2017 15:33:59 -0700	[thread overview]
Message-ID: <20170828153359.f9b252f99647eebd339a3a89@linux-foundation.org> (raw)
In-Reply-To: <20170828093341.26341-1-mhocko@kernel.org>

On Mon, 28 Aug 2017 11:33:41 +0200 Michal Hocko <mhocko@kernel.org> wrote:

> drain_all_pages backs off when called from a kworker context since
> 0ccce3b924212 ("mm, page_alloc: drain per-cpu pages from workqueue
> context") because the original IPI based pcp draining has been replaced
> by a WQ based one and the check wanted to prevent from recursion and
> inter workers dependencies. This has made some sense at the time
> because the system WQ has been used and one worker holding the lock
> could be blocked while waiting for new workers to emerge which can be a
> problem under OOM conditions.
> 
> Since then ce612879ddc7 ("mm: move pcp and lru-pcp draining into single
> wq") has moved draining to a dedicated (mm_percpu_wq) WQ with a rescuer
> so we shouldn't depend on any other WQ activity to make a forward
> progress so calling drain_all_pages from a worker context is safe as
> long as this doesn't happen from mm_percpu_wq itself which is not the
> case because all workers are required to _not_ depend on any MM locks.
> 
> Why is this a problem in the first place? ACPI driven memory hot-remove
> (acpi_device_hotplug) is executed from the worker context. We end
> up calling __offline_pages to free all the pages and that requires
> both lru_add_drain_all_cpuslocked and drain_all_pages to do their job
> otherwise we can have dangling pages on pcp lists and fail the offline
> operation (__test_page_isolated_in_pageblock would see a page with 0
> ref. count but without PageBuddy set).
> 
> Fix the issue by removing the worker check in drain_all_pages.
> lru_add_drain_all_cpuslocked doesn't have this restriction so it works
> as expected.
> 
> Fixes: 0ccce3b924212 ("mm, page_alloc: drain per-cpu pages from workqueue context")
> Signed-off-by: Michal Hocko <mhocko@suse.com>

No cc:stable?

--
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>

  reply	other threads:[~2017-08-28 22:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28  9:33 [PATCH] mm, memory_hotplug: do not back off draining pcp free pages from kworker context Michal Hocko
2017-08-28 22:33 ` Andrew Morton [this message]
2017-08-29 11:20   ` Tetsuo Handa
2017-08-29 11:28     ` Michal Hocko
2017-08-31  5:33       ` Michal Hocko
2017-09-19  3:38         ` Tejun Heo
2017-09-19  9:45           ` Michal Hocko
2017-09-19 18:57             ` Tejun Heo
2017-08-29 13:53   ` 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=20170828153359.f9b252f99647eebd339a3a89@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    --cc=mhocko@suse.com \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).