From: kernel test robot <lkp@intel.com>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jlelli:upstream/deadline/domains-suspend 2/4] kernel/sched/rt.c:2913:14: error: use of undeclared identifier 'sched_domains_mutex'
Date: Thu, 27 Feb 2025 05:52:32 +0800 [thread overview]
Message-ID: <202502270513.eQknwYIs-lkp@intel.com> (raw)
tree: https://github.com/jlelli/linux.git upstream/deadline/domains-suspend
head: 78c2e4083eeedc3526f07bedfca514eefbe45e38
commit: dfdff94e7f88b77e61e6cf8ec6aeea320fa12e7e [2/4] sched/deadline: Generalize unique visiting of root domains
config: x86_64-buildonly-randconfig-002-20250227 (https://download.01.org/0day-ci/archive/20250227/202502270513.eQknwYIs-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250227/202502270513.eQknwYIs-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/202502270513.eQknwYIs-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/sched/build_policy.c:52:
>> kernel/sched/rt.c:2913:14: error: use of undeclared identifier 'sched_domains_mutex'
2913 | mutex_lock(&sched_domains_mutex);
| ^
kernel/sched/rt.c:2940:16: error: use of undeclared identifier 'sched_domains_mutex'
2940 | mutex_unlock(&sched_domains_mutex);
| ^
2 errors generated.
vim +/sched_domains_mutex +2913 kernel/sched/rt.c
2904
2905 static int sched_rt_handler(const struct ctl_table *table, int write, void *buffer,
2906 size_t *lenp, loff_t *ppos)
2907 {
2908 int old_period, old_runtime;
2909 static DEFINE_MUTEX(mutex);
2910 int ret;
2911
2912 mutex_lock(&mutex);
> 2913 mutex_lock(&sched_domains_mutex);
2914 old_period = sysctl_sched_rt_period;
2915 old_runtime = sysctl_sched_rt_runtime;
2916
2917 ret = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
2918
2919 if (!ret && write) {
2920 ret = sched_rt_global_validate();
2921 if (ret)
2922 goto undo;
2923
2924 ret = sched_dl_global_validate();
2925 if (ret)
2926 goto undo;
2927
2928 ret = sched_rt_global_constraints();
2929 if (ret)
2930 goto undo;
2931
2932 sched_rt_do_global();
2933 sched_dl_do_global();
2934 }
2935 if (0) {
2936 undo:
2937 sysctl_sched_rt_period = old_period;
2938 sysctl_sched_rt_runtime = old_runtime;
2939 }
2940 mutex_unlock(&sched_domains_mutex);
2941 mutex_unlock(&mutex);
2942
2943 return ret;
2944 }
2945
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-26 21:52 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=202502270513.eQknwYIs-lkp@intel.com \
--to=lkp@intel.com \
--cc=juri.lelli@redhat.com \
--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