linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chen Ridong <chenridong@huaweicloud.com>
To: kernel test robot <lkp@intel.com>,
	hannes@cmpxchg.org, mhocko@kernel.org, roman.gushchin@linux.dev,
	shakeel.butt@linux.dev, muchun.song@linux.dev,
	akpm@linux-foundation.org, axelrasmussen@google.com,
	yuanchu@google.com, weixugc@google.com, david@kernel.org,
	zhengqi.arch@bytedance.com, lorenzo.stoakes@oracle.com
Cc: oe-kbuild-all@lists.linux.dev, cgroups@vger.kernel.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	lujialin4@huawei.com
Subject: Re: [PATCH -next 2/2] memcg: remove mem_cgroup_size()
Date: Wed, 10 Dec 2025 11:06:55 +0800	[thread overview]
Message-ID: <1189acd5-4908-4a51-a7bc-8b52a8489140@huaweicloud.com> (raw)
In-Reply-To: <202512100924.LqJqXM7P-lkp@intel.com>



On 2025/12/10 9:35, kernel test robot wrote:
> Hi Chen,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on next-20251209]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Chen-Ridong/memcg-move-mem_cgroup_usage-memcontrol-v1-c/20251209-211854
> base:   next-20251209
> patch link:    https://lore.kernel.org/r/20251209130251.1988615-3-chenridong%40huaweicloud.com
> patch subject: [PATCH -next 2/2] memcg: remove mem_cgroup_size()
> config: i386-allnoconfig (https://download.01.org/0day-ci/archive/20251210/202512100924.LqJqXM7P-lkp@intel.com/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251210/202512100924.LqJqXM7P-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/202512100924.LqJqXM7P-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>    mm/vmscan.c: In function 'apply_proportional_protection':
>>> mm/vmscan.c:2488:63: error: invalid use of undefined type 'struct mem_cgroup'
>     2488 |                 unsigned long usage = page_counter_read(&memcg->memory);
>          |                                                               ^~
> 
> 
> vim +2488 mm/vmscan.c
> 

Oh, I missed CONFIG_MEMCG=n case, will fix it, thanks.

-- 
Best regards,
Ridong



      reply	other threads:[~2025-12-10  3:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09 13:02 [PATCH -next 0/2] memcg cleanups Chen Ridong
2025-12-09 13:02 ` [PATCH -next 1/2] memcg: move mem_cgroup_usage memcontrol-v1.c Chen Ridong
2025-12-09 13:02 ` [PATCH -next 2/2] memcg: remove mem_cgroup_size() Chen Ridong
2025-12-10  1:35   ` kernel test robot
2025-12-10  1:35   ` kernel test robot
2025-12-10  3:06     ` Chen Ridong [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=1189acd5-4908-4a51-a7bc-8b52a8489140@huaweicloud.com \
    --to=chenridong@huaweicloud.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=cgroups@vger.kernel.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=lujialin4@huawei.com \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=weixugc@google.com \
    --cc=yuanchu@google.com \
    --cc=zhengqi.arch@bytedance.com \
    /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