From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Jiri Slaby <jslaby@suse.cz>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: <cgroups@vger.kernel.org>
Cc: <stable@vger.kernel.org>
Cc: <linux-mm@kvack.org>
Cc: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH -resend v2] memcg: make it work on sparse non-0-node systems
Date: Wed, 29 May 2019 13:14:49 +0000 [thread overview]
Message-ID: <20190529131451.0599B205F4@mail.kernel.org> (raw)
In-Reply-To: <20190522091940.3615-1-jslaby@suse.cz>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 60d3fd32a7a9d list_lru: introduce per-memcg lists.
The bot has tested the following trees: v5.1.4, v5.0.18, v4.19.45, v4.14.121, v4.9.178, v4.4.180.
v5.1.4: Build OK!
v5.0.18: Build OK!
v4.19.45: Build OK!
v4.14.121: Failed to apply! Possible dependencies:
0200894d11551 ("new helper: destroy_unused_super()")
2b3648a6ff83b ("fs/super.c: refactor alloc_super()")
39887653aab4c ("mm/workingset.c: refactor workingset_init()")
8e04944f0ea8b ("mm,vmscan: Allow preallocating memory for register_shrinker().")
c92e8e10cafea ("fs: propagate shrinker::id to list_lru")
v4.9.178: Failed to apply! Possible dependencies:
0200894d11551 ("new helper: destroy_unused_super()")
14b468791fa95 ("mm: workingset: move shadow entry tracking to radix tree exceptional tracking")
2b3648a6ff83b ("fs/super.c: refactor alloc_super()")
39887653aab4c ("mm/workingset.c: refactor workingset_init()")
4d693d08607ab ("lib: radix-tree: update callback for changing leaf nodes")
6d75f366b9242 ("lib: radix-tree: check accounting of existing slot replacement users")
8e04944f0ea8b ("mm,vmscan: Allow preallocating memory for register_shrinker().")
c92e8e10cafea ("fs: propagate shrinker::id to list_lru")
f4b109c6dad54 ("lib: radix-tree: add entry deletion support to __radix_tree_replace()")
f7942430e40f1 ("lib: radix-tree: native accounting of exceptional entries")
v4.4.180: Failed to apply! Possible dependencies:
0200894d11551 ("new helper: destroy_unused_super()")
0cefabdaf757a ("mm: workingset: fix premature shadow node shrinking with cgroups")
0e749e54244ee ("dax: increase granularity of dax_clear_blocks() operations")
14b468791fa95 ("mm: workingset: move shadow entry tracking to radix tree exceptional tracking")
162453bfbdf4c ("mm: workingset: separate shadow unpacking and refault calculation")
2b3648a6ff83b ("fs/super.c: refactor alloc_super()")
39887653aab4c ("mm/workingset.c: refactor workingset_init()")
52db400fcd502 ("pmem, dax: clean up clear_pmem()")
612e44939c3c7 ("mm: workingset: eviction buckets for bigmem/lowbit machines")
689c94f03ae25 ("mm: workingset: #define radix entry eviction mask")
6e4eab577a0ca ("fs: Add user namespace member to struct super_block")
8e04944f0ea8b ("mm,vmscan: Allow preallocating memory for register_shrinker().")
ac401cc782429 ("dax: New fault locking")
b2e0d1625e193 ("dax: fix lifetime of in-kernel dax mappings with dax_map_atomic()")
c92e8e10cafea ("fs: propagate shrinker::id to list_lru")
d91ee87d8d85a ("vfs: Pass data, ns, and ns->userns to mount_ns")
e4b2749158631 ("DAX: move RADIX_DAX_ definitions to dax.c")
f7942430e40f1 ("lib: radix-tree: native accounting of exceptional entries")
f9fe48bece3af ("dax: support dirty DAX entries in radix tree")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-05-29 13:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 8:16 memcg causes crashes in list_lru_add Jiri Slaby
2019-04-29 9:25 ` Jiri Slaby
2019-04-29 10:09 ` Jiri Slaby
2019-04-29 10:40 ` Michal Hocko
2019-04-29 10:43 ` Michal Hocko
2019-04-29 10:59 ` [PATCH] memcg: make it work on sparse non-0-node systems Jiri Slaby
2019-04-29 11:30 ` Michal Hocko
2019-04-29 11:55 ` Jiri Slaby
2019-04-29 12:11 ` Jiri Slaby
2019-04-29 13:15 ` Michal Hocko
2019-05-09 7:21 ` Jiri Slaby
2019-05-09 12:25 ` Vladimir Davydov
2019-05-09 16:05 ` Shakeel Butt
2019-05-16 13:59 ` Michal Hocko
2019-05-17 4:48 ` Jiri Slaby
2019-05-17 8:00 ` Vladimir Davydov
2019-05-17 8:16 ` Jiri Slaby
2019-05-17 11:42 ` [PATCH v2] " Jiri Slaby
2019-05-17 12:13 ` Shakeel Butt
2019-05-17 12:27 ` Michal Hocko
2019-05-22 9:19 ` [PATCH -resend " Jiri Slaby
2019-05-29 13:14 ` Sasha Levin [this message]
2019-04-29 10:17 ` memcg causes crashes in list_lru_add 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=20190529131451.0599B205F4@mail.kernel.org \
--to=sashal@kernel.org \
--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