From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: mmotm 2019-07-04-15-01 uploaded (mm/vmscan.c)
Date: Thu, 4 Jul 2019 20:01:06 -0700 [thread overview]
Message-ID: <9cbdb785-b51d-9419-6b9a-ec282a4e4fa2@infradead.org> (raw)
In-Reply-To: <20190704220152.1bF4q6uyw%akpm@linux-foundation.org>
On 7/4/19 3:01 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2019-07-04-15-01 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
on i386:
CONFIG_SLOB=y <<<<<<<<<<
../mm/vmscan.c: In function ‘prealloc_memcg_shrinker’:
../mm/vmscan.c:220:3: error: implicit declaration of function ‘memcg_expand_shrinker_maps’ [-Werror=implicit-function-declaration]
if (memcg_expand_shrinker_maps(id)) {
^
In file included from ../include/linux/rbtree.h:22:0,
from ../include/linux/mm_types.h:10,
from ../include/linux/mmzone.h:21,
from ../include/linux/gfp.h:6,
from ../include/linux/mm.h:10,
from ../mm/vmscan.c:17:
../mm/vmscan.c: In function ‘shrink_slab_memcg’:
../mm/vmscan.c:608:54: error: ‘struct mem_cgroup_per_node’ has no member named ‘shrinker_map’
map = rcu_dereference_protected(memcg->nodeinfo[nid]->shrinker_map,
^
../include/linux/rcupdate.h:321:12: note: in definition of macro ‘__rcu_dereference_protected’
((typeof(*p) __force __kernel *)(p)); \
^
../mm/vmscan.c:608:8: note: in expansion of macro ‘rcu_dereference_protected’
map = rcu_dereference_protected(memcg->nodeinfo[nid]->shrinker_map,
^
../mm/vmscan.c:608:54: error: ‘struct mem_cgroup_per_node’ has no member named ‘shrinker_map’
map = rcu_dereference_protected(memcg->nodeinfo[nid]->shrinker_map,
^
../include/linux/rcupdate.h:321:35: note: in definition of macro ‘__rcu_dereference_protected’
((typeof(*p) __force __kernel *)(p)); \
^
../mm/vmscan.c:608:8: note: in expansion of macro ‘rcu_dereference_protected’
map = rcu_dereference_protected(memcg->nodeinfo[nid]->shrinker_map,
^
--
~Randy
prev parent reply other threads:[~2019-07-05 3:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 22:01 mmotm 2019-07-04-15-01 uploaded akpm
2019-07-05 1:09 ` mmotm 2019-07-04-15-01 uploaded (gpu/drm/i915/oa/) Randy Dunlap
2019-07-05 1:19 ` Randy Dunlap
2019-07-05 3:05 ` Masahiro Yamada
2019-07-05 3:09 ` Masahiro Yamada
2019-07-05 3:23 ` Randy Dunlap
2019-07-05 3:44 ` Masahiro Yamada
2019-07-05 4:09 ` Randy Dunlap
2019-07-31 13:21 ` Jani Nikula
2019-07-05 3:14 ` Stephen Rothwell
2019-07-05 5:09 ` Andrew Morton
2019-07-05 5:22 ` Joe Perches
2019-07-05 5:29 ` Andrew Morton
2019-07-05 3:01 ` Randy Dunlap [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=9cbdb785-b51d-9419-6b9a-ec282a4e4fa2@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).