From: Dan Carpenter <dan.carpenter@linaro.org>
To: oe-kbuild@lists.linux.dev,
Zhongkun He <hezhongkun.hzk@bytedance.com>,
akpm@linux-foundation.org, tytso@mit.edu, jack@suse.com,
hannes@cmpxchg.org, mhocko@kernel.org
Cc: lkp@intel.com, oe-kbuild-all@lists.linux.dev,
muchun.song@linux.dev, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org,
Zhongkun He <hezhongkun.hzk@bytedance.com>,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH 1/2] mm: memcg: introduce PF_MEMALLOC_ACCOUNTFORCE to postpone reclaim to return-to-userland path
Date: Tue, 24 Jun 2025 17:47:14 +0300 [thread overview]
Message-ID: <400e2b89-1ad7-4626-9ee0-e45a9e5b5227@suswa.mountain> (raw)
In-Reply-To: <71a4bbc284048ceb38eaac53dfa1031f92ac52b7.1750234270.git.hezhongkun.hzk@bytedance.com>
Hi Zhongkun,
kernel test robot noticed the following build warnings:
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Zhongkun-He/mm-memcg-introduce-PF_MEMALLOC_ACCOUNTFORCE-to-postpone-reclaim-to-return-to-userland-path/20250618-194101
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/71a4bbc284048ceb38eaac53dfa1031f92ac52b7.1750234270.git.hezhongkun.hzk%40bytedance.com
patch subject: [PATCH 1/2] mm: memcg: introduce PF_MEMALLOC_ACCOUNTFORCE to postpone reclaim to return-to-userland path
config: i386-randconfig-141-20250619 (https://download.01.org/0day-ci/archive/20250624/202506242032.uShv7ASV-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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>
| Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
| Closes: https://lore.kernel.org/r/202506242032.uShv7ASV-lkp@intel.com/
smatch warnings:
mm/memcontrol.c:2341 mem_cgroup_handle_over_max() warn: use 'gfp_mask' here instead of GFP_KERNEL?
vim +/gfp_mask +2341 mm/memcontrol.c
b5db553cc19549 Zhongkun He 2025-06-18 2320 void mem_cgroup_handle_over_max(gfp_t gfp_mask)
^^^^^^^^
b5db553cc19549 Zhongkun He 2025-06-18 2321 {
b5db553cc19549 Zhongkun He 2025-06-18 2322 unsigned long nr_reclaimed = 0;
b5db553cc19549 Zhongkun He 2025-06-18 2323 unsigned int nr_pages = current->memcg_nr_pages_over_max;
b5db553cc19549 Zhongkun He 2025-06-18 2324 int nr_retries = MAX_RECLAIM_RETRIES;
b5db553cc19549 Zhongkun He 2025-06-18 2325 struct mem_cgroup *memcg, *mem_over_limit;
b5db553cc19549 Zhongkun He 2025-06-18 2326
b5db553cc19549 Zhongkun He 2025-06-18 2327 if (likely(!nr_pages))
b5db553cc19549 Zhongkun He 2025-06-18 2328 return;
b5db553cc19549 Zhongkun He 2025-06-18 2329
b5db553cc19549 Zhongkun He 2025-06-18 2330 memcg = get_mem_cgroup_from_mm(current->mm);
b5db553cc19549 Zhongkun He 2025-06-18 2331 current->memcg_nr_pages_over_max = 0;
b5db553cc19549 Zhongkun He 2025-06-18 2332
b5db553cc19549 Zhongkun He 2025-06-18 2333 retry:
b5db553cc19549 Zhongkun He 2025-06-18 2334 mem_over_limit = get_over_limit_memcg(memcg);
b5db553cc19549 Zhongkun He 2025-06-18 2335 if (!mem_over_limit)
b5db553cc19549 Zhongkun He 2025-06-18 2336 goto out;
b5db553cc19549 Zhongkun He 2025-06-18 2337
b5db553cc19549 Zhongkun He 2025-06-18 2338 while (nr_reclaimed < nr_pages) {
b5db553cc19549 Zhongkun He 2025-06-18 2339 unsigned long reclaimed;
b5db553cc19549 Zhongkun He 2025-06-18 2340
b5db553cc19549 Zhongkun He 2025-06-18 @2341 reclaimed = try_to_free_mem_cgroup_pages(mem_over_limit,
b5db553cc19549 Zhongkun He 2025-06-18 2342 nr_pages, GFP_KERNEL,
I guess GFP_KERNEL is fine. The gfp_mask is used below. Don't worry
about this one if the GFP_KERNEL is intended. Just ignore the warning
message.
b5db553cc19549 Zhongkun He 2025-06-18 2343 MEMCG_RECLAIM_MAY_SWAP,
b5db553cc19549 Zhongkun He 2025-06-18 2344 NULL);
b5db553cc19549 Zhongkun He 2025-06-18 2345
b5db553cc19549 Zhongkun He 2025-06-18 2346 if (!reclaimed && !nr_retries--)
b5db553cc19549 Zhongkun He 2025-06-18 2347 break;
b5db553cc19549 Zhongkun He 2025-06-18 2348
b5db553cc19549 Zhongkun He 2025-06-18 2349 nr_reclaimed += reclaimed;
b5db553cc19549 Zhongkun He 2025-06-18 2350 }
b5db553cc19549 Zhongkun He 2025-06-18 2351
b5db553cc19549 Zhongkun He 2025-06-18 2352 if ((nr_reclaimed < nr_pages) &&
b5db553cc19549 Zhongkun He 2025-06-18 2353 (page_counter_read(&mem_over_limit->memory) >
b5db553cc19549 Zhongkun He 2025-06-18 2354 READ_ONCE(mem_over_limit->memory.max)) &&
b5db553cc19549 Zhongkun He 2025-06-18 2355 mem_cgroup_oom(mem_over_limit, gfp_mask,
b5db553cc19549 Zhongkun He 2025-06-18 2356 get_order((nr_pages - nr_reclaimed) * PAGE_SIZE))) {
b5db553cc19549 Zhongkun He 2025-06-18 2357 nr_retries = MAX_RECLAIM_RETRIES;
b5db553cc19549 Zhongkun He 2025-06-18 2358 goto retry;
b5db553cc19549 Zhongkun He 2025-06-18 2359 }
b5db553cc19549 Zhongkun He 2025-06-18 2360
b5db553cc19549 Zhongkun He 2025-06-18 2361 out:
b5db553cc19549 Zhongkun He 2025-06-18 2362 css_put(&memcg->css);
b5db553cc19549 Zhongkun He 2025-06-18 2363 }
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-24 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 11:39 [PATCH 0/2] Postpone memcg reclaim to return-to-user path Zhongkun He
2025-06-18 11:39 ` [PATCH 1/2] mm: memcg: introduce PF_MEMALLOC_ACCOUNTFORCE to postpone reclaim to return-to-userland path Zhongkun He
2025-06-24 14:47 ` Dan Carpenter [this message]
2025-06-18 11:39 ` [PATCH 2/2] jbd2: mark the transaction context with the scope PF_MEMALLOC_ACFORCE context Zhongkun He
2025-06-18 22:37 ` [PATCH 0/2] Postpone memcg reclaim to return-to-user path Shakeel Butt
2025-06-19 8:04 ` Jan Kara
2025-06-24 7:45 ` [External] " Zhongkun He
2025-06-24 7:44 ` Zhongkun He
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=400e2b89-1ad7-4626-9ee0-e45a9e5b5227@suswa.mountain \
--to=dan.carpenter@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hezhongkun.hzk@bytedance.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=songmuchun@bytedance.com \
--cc=tytso@mit.edu \
/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