From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: David Hildenbrand <david@redhat.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, David Hildenbrand <david@redhat.com>,
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@techsingularity.net>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Jan Kara <jack@suse.cz>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Vratislav Bendel <vbendel@redhat.com>
Cc: Rafael Aquini <aquini@redhat.com>
Cc: Konstantin Khlebnikov <k.khlebnikov@samsung.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2] mm: migrate: don't rely on __PageMovable() of newpage after unlocking it
Date: Thu, 31 Jan 2019 02:04:47 +0000 [thread overview]
Message-ID: <20190131020448.072FE218AF@mail.kernel.org> (raw)
In-Reply-To: <20190129233217.10747-1-david@redhat.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: d6d86c0a7f8d mm/balloon_compaction: redesign ballooned pages management.
The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96, v4.9.153, v4.4.172, v3.18.133.
v4.20.5: Build OK!
v4.19.18: Build OK!
v4.14.96: Build OK!
v4.9.153: Build OK!
v4.4.172: Failed to apply! Possible dependencies:
1031bc589228 ("lib/vsprintf: add %*pg format specifier")
14e0a214d62d ("tools, perf: make gfp_compact_table up to date")
1f7866b4aebd ("mm, tracing: make show_gfp_flags() up to date")
420adbe9fc1a ("mm, tracing: unify mm flags handling in tracepoints and printk")
53f9263baba6 ("mm: rework mapcount accounting to enable 4k mapping of THPs")
7cd12b4abfd2 ("mm, page_owner: track and print last migrate reason")
7d2eba0557c1 ("mm: add tracepoint for scanning pages")
c6c919eb90e0 ("mm: use put_page() to free page instead of putback_lru_page()")
d435edca9288 ("mm, page_owner: copy page owner info during migration")
d8c1bdeb5d6b ("page-flags: trivial cleanup for PageTrans* helpers")
eca56ff906bd ("mm, shmem: add internal shmem resident memory accounting")
edf14cdbf9a0 ("mm, printk: introduce new format string for flags")
v3.18.133: Failed to apply! Possible dependencies:
2847cf95c68f ("mm/debug-pagealloc: cleanup page guard code")
48c96a368579 ("mm/page_owner: keep track of page owners")
7cd12b4abfd2 ("mm, page_owner: track and print last migrate reason")
94f759d62b2c ("mm/page_owner.c: remove unnecessary stack_trace field")
c6c919eb90e0 ("mm: use put_page() to free page instead of putback_lru_page()")
d435edca9288 ("mm, page_owner: copy page owner info during migration")
e2cfc91120fa ("mm/page_owner: set correct gfp_mask on page_owner")
e30825f1869a ("mm/debug-pagealloc: prepare boottime configurable on/off")
eefa864b701d ("mm/page_ext: resurrect struct page extending code for debugging")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-01-31 2:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 23:32 [PATCH v2] mm: migrate: don't rely on __PageMovable() of newpage after unlocking it David Hildenbrand
2019-01-31 2:04 ` Sasha Levin [this message]
2019-02-01 13:43 ` [PATCH v2 for-4.4-stable] " David Hildenbrand
2019-02-01 14:09 ` Greg KH
2019-02-01 14:18 ` David Hildenbrand
2019-02-01 14:27 ` David Hildenbrand
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=20190131020448.072FE218AF@mail.kernel.org \
--to=sashal@kernel.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.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).