From: kernel test robot <lkp@intel.com>
To: Kaiyang Zhao <kaiyang2@cs.cmu.edu>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-unstable 216/222] mm/memcontrol.c:993: warning: Function parameter or struct member 'folio' not described in 'get_mem_cgroup_from_folio'
Date: Sun, 11 Aug 2024 08:24:18 +0800 [thread overview]
Message-ID: <202408110848.pqaWv5zD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: 7d7894afcca68b40bfca49f4d1303167d224919e
commit: 24f8717a5d0bedc9664cf242b14a31c18f9351a6 [216/222] mm,memcg: provide per-cgroup counters for NUMA balancing operations
config: arc-randconfig-002-20240811 (https://download.01.org/0day-ci/archive/20240811/202408110848.pqaWv5zD-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240811/202408110848.pqaWv5zD-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/202408110848.pqaWv5zD-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/memcontrol.c:993: warning: Function parameter or struct member 'folio' not described in 'get_mem_cgroup_from_folio'
vim +993 mm/memcontrol.c
988
989 /**
990 * get_mem_cgroup_from_folio - Obtain a reference on a given folio's memcg.
991 */
992 struct mem_cgroup *get_mem_cgroup_from_folio(struct folio *folio)
> 993 {
994 struct mem_cgroup *memcg = folio_memcg(folio);
995
996 if (mem_cgroup_disabled())
997 return NULL;
998
999 rcu_read_lock();
1000 if (!memcg || WARN_ON_ONCE(!css_tryget(&memcg->css)))
1001 memcg = root_mem_cgroup;
1002 rcu_read_unlock();
1003 return memcg;
1004 }
1005
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-11 0:25 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=202408110848.pqaWv5zD-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kaiyang2@cs.cmu.edu \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox