From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Gregory Price <gourry@gourry.net>
Subject: [gourryinverse:scratch/gourry/isolation/linus 6/10] kernel/cgroup/cpuset.c:2812:46: error: too many arguments to function call, expected single argument 'nodes', have 2 arguments
Date: Tue, 11 Nov 2025 23:00:08 +0800 [thread overview]
Message-ID: <202511112239.aI1ulpX0-lkp@intel.com> (raw)
tree: https://github.com/gourryinverse/linux scratch/gourry/isolation/linus
head: c74a85115777a0e4ff7ba671c4631adb4ba32ecc
commit: 81b4628c13856d1bc84678ed6655180ca0554688 [6/10] cpuset: introduce cpuset.mems.default
config: i386-defconfig (https://download.01.org/0day-ci/archive/20251111/202511112239.aI1ulpX0-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/20251111/202511112239.aI1ulpX0-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/202511112239.aI1ulpX0-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/cgroup/cpuset.c:2812:46: error: too many arguments to function call, expected single argument 'nodes', have 2 arguments
2812 | mt_nodemask_sysram_mask(&cp->mems_default, &cp->effective_mems);
| ~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
include/linux/memory-tiers.h:99:20: note: 'mt_nodemask_sysram_mask' declared here
99 | static inline void mt_nodemask_sysram_mask(nodemask_t *nodes) { return; }
| ^ ~~~~~~~~~~~~~~~~~
kernel/cgroup/cpuset.c:3599:46: error: too many arguments to function call, expected single argument 'nodes', have 2 arguments
3599 | mt_nodemask_sysram_mask(&cs->mems_default, &cs->effective_mems);
| ~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
include/linux/memory-tiers.h:99:20: note: 'mt_nodemask_sysram_mask' declared here
99 | static inline void mt_nodemask_sysram_mask(nodemask_t *nodes) { return; }
| ^ ~~~~~~~~~~~~~~~~~
kernel/cgroup/cpuset.c:3631:45: error: too many arguments to function call, expected single argument 'nodes', have 2 arguments
3631 | mt_nodemask_sysram_mask(&cs->mems_default, &cs->effective_mems);
| ~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
include/linux/memory-tiers.h:99:20: note: 'mt_nodemask_sysram_mask' declared here
99 | static inline void mt_nodemask_sysram_mask(nodemask_t *nodes) { return; }
| ^ ~~~~~~~~~~~~~~~~~
kernel/cgroup/cpuset.c:3835:5: error: too many arguments to function call, expected single argument 'nodes', have 2 arguments
3834 | mt_nodemask_sysram_mask(&top_cpuset.mems_default,
| ~~~~~~~~~~~~~~~~~~~~~~~
3835 | &top_cpuset.effective_mems);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/memory-tiers.h:99:20: note: 'mt_nodemask_sysram_mask' declared here
99 | static inline void mt_nodemask_sysram_mask(nodemask_t *nodes) { return; }
| ^ ~~~~~~~~~~~~~~~~~
kernel/cgroup/cpuset.c:3865:45: error: too many arguments to function call, expected single argument 'nodes', have 2 arguments
3865 | mt_nodemask_sysram_mask(&cs->mems_default, &cs->effective_mems);
| ~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~
include/linux/memory-tiers.h:99:20: note: 'mt_nodemask_sysram_mask' declared here
99 | static inline void mt_nodemask_sysram_mask(nodemask_t *nodes) { return; }
| ^ ~~~~~~~~~~~~~~~~~
kernel/cgroup/cpuset.c:4058:6: error: too many arguments to function call, expected single argument 'nodes', have 2 arguments
4057 | mt_nodemask_sysram_mask(&top_cpuset.mems_default,
| ~~~~~~~~~~~~~~~~~~~~~~~
4058 | &top_cpuset.effective_mems);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/memory-tiers.h:99:20: note: 'mt_nodemask_sysram_mask' declared here
99 | static inline void mt_nodemask_sysram_mask(nodemask_t *nodes) { return; }
| ^ ~~~~~~~~~~~~~~~~~
kernel/cgroup/cpuset.c:4130:5: error: too many arguments to function call, expected single argument 'nodes', have 2 arguments
4129 | mt_nodemask_sysram_mask(&top_cpuset.mems_default,
| ~~~~~~~~~~~~~~~~~~~~~~~
4130 | &top_cpuset.effective_mems);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/memory-tiers.h:99:20: note: 'mt_nodemask_sysram_mask' declared here
99 | static inline void mt_nodemask_sysram_mask(nodemask_t *nodes) { return; }
| ^ ~~~~~~~~~~~~~~~~~
7 errors generated.
vim +/nodes +2812 kernel/cgroup/cpuset.c
2769
2770 /*
2771 * update_nodemasks_hier - Update effective nodemasks and tasks in the subtree
2772 * @cs: the cpuset to consider
2773 * @new_mems: a temp variable for calculating new effective_mems
2774 *
2775 * When configured nodemask is changed, the effective nodemasks of this cpuset
2776 * and all its descendants need to be updated.
2777 *
2778 * On legacy hierarchy, effective_mems will be the same with mems_allowed.
2779 *
2780 * Called with cpuset_mutex held
2781 */
2782 static void update_nodemasks_hier(struct cpuset *cs, nodemask_t *new_mems)
2783 {
2784 struct cpuset *cp;
2785 struct cgroup_subsys_state *pos_css;
2786
2787 rcu_read_lock();
2788 cpuset_for_each_descendant_pre(cp, pos_css, cs) {
2789 struct cpuset *parent = parent_cs(cp);
2790
2791 nodes_and(*new_mems, cp->mems_allowed, parent->effective_mems);
2792
2793 /*
2794 * If it becomes empty, inherit the effective mask of the
2795 * parent, which is guaranteed to have some MEMs.
2796 */
2797 if (is_in_v2_mode() && nodes_empty(*new_mems))
2798 *new_mems = parent->effective_mems;
2799
2800 /* Skip the whole subtree if the nodemask remains the same. */
2801 if (nodes_equal(*new_mems, cp->effective_mems)) {
2802 pos_css = css_rightmost_descendant(pos_css);
2803 continue;
2804 }
2805
2806 if (!css_tryget_online(&cp->css))
2807 continue;
2808 rcu_read_unlock();
2809
2810 spin_lock_irq(&callback_lock);
2811 cp->effective_mems = *new_mems;
> 2812 mt_nodemask_sysram_mask(&cp->mems_default, &cp->effective_mems);
2813 spin_unlock_irq(&callback_lock);
2814
2815 WARN_ON(!is_in_v2_mode() &&
2816 !nodes_equal(cp->mems_allowed, cp->effective_mems));
2817
2818 cpuset_update_tasks_nodemask(cp);
2819
2820 rcu_read_lock();
2821 css_put(&cp->css);
2822 }
2823 rcu_read_unlock();
2824 }
2825
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-11 15: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=202511112239.aI1ulpX0-lkp@intel.com \
--to=lkp@intel.com \
--cc=gourry@gourry.net \
--cc=llvm@lists.linux.dev \
--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