From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Liu Shixin <liushixin2@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 2613/2613] mm/dynamic_pool.c:118:55: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Fri, 1 Aug 2025 07:01:10 +0800 [thread overview]
Message-ID: <202508010611.7SCGF7vt-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: 27e11e2b193b780ecfb0c4f0d0a73a0a28879c20
commit: 8822f3476adadcf84c7cb3db0d1a0a39a6fdc398 [2613/2613] mm/dynamic_pool: introduce per-memcg memory pool
config: x86_64-randconfig-r113-20250801 (https://download.01.org/0day-ci/archive/20250801/202508010611.7SCGF7vt-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250801/202508010611.7SCGF7vt-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202508010611.7SCGF7vt-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/dynamic_pool.c:118:55: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct cgroup_subsys_state *css @@ got struct cgroup_subsys_state [noderef] __rcu * @@
mm/dynamic_pool.c:118:55: sparse: expected struct cgroup_subsys_state *css
mm/dynamic_pool.c:118:55: sparse: got struct cgroup_subsys_state [noderef] __rcu *
vim +118 mm/dynamic_pool.c
115
116 int dynamic_pool_destroy(struct cgroup *cgrp, bool *clear_css_online)
117 {
> 118 struct cgroup_subsys_state *css = cgrp->subsys[memory_cgrp_id];
119 struct mem_cgroup *memcg = mem_cgroup_from_css(css);
120 struct dynamic_pool *dpool;
121 int ret = 0;
122
123 if (!dpool_enabled || !memcg)
124 return 0;
125
126 mutex_lock(&dpool_mutex);
127 dpool = dpool_get_from_memcg(memcg);
128 if (!dpool)
129 goto unlock;
130
131 if (dpool->memcg != memcg) {
132 memcg->dpool = NULL;
133 goto put;
134 }
135
136 /* A offline dpool is not allowed for allocation */
137 dpool->online = false;
138
139 memcg->dpool = NULL;
140
141 /* Release the initial reference count */
142 dpool_put(dpool);
143
144 /*
145 * Since dpool is destroyed and the memcg will be freed then,
146 * clear CSS_ONLINE immediately to prevent race with create.
147 */
148 if (cgrp->self.flags & CSS_ONLINE) {
149 cgrp->self.flags &= ~CSS_ONLINE;
150 *clear_css_online = true;
151 }
152
153 put:
154 dpool_put(dpool);
155 unlock:
156 mutex_unlock(&dpool_mutex);
157
158 return ret;
159 }
160
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-31 23:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202508010611.7SCGF7vt-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=liushixin2@huawei.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.