From: kernel test robot <lkp@intel.com>
To: Baisong Zhong <zhongbaisong@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>
Subject: kernel/sched/rt.c:9:18: warning: 'max_rt_runtime' defined but not used
Date: Sun, 22 Dec 2024 09:22:14 +0800 [thread overview]
Message-ID: <202412220957.YMZbEEtD-lkp@intel.com> (raw)
Hi Baisong,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: e84a3bf7f4aa669c05e3884497774148ac111468
commit: 28f152cd0926596e69d412467b11b6fe6fe4e864 sched/rt: fix build error when CONFIG_SYSCTL is disable
date: 2 years, 9 months ago
config: s390-randconfig-002-20241220 (https://download.01.org/0day-ci/archive/20241222/202412220957.YMZbEEtD-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241222/202412220957.YMZbEEtD-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/202412220957.YMZbEEtD-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from kernel/sched/build_policy.c:43:
kernel/sched/rt.c:309:6: warning: no previous prototype for 'unregister_rt_sched_group' [-Wmissing-prototypes]
309 | void unregister_rt_sched_group(struct task_group *tg) { }
| ^~~~~~~~~~~~~~~~~~~~~~~~~
kernel/sched/rt.c:311:6: warning: no previous prototype for 'free_rt_sched_group' [-Wmissing-prototypes]
311 | void free_rt_sched_group(struct task_group *tg) { }
| ^~~~~~~~~~~~~~~~~~~
kernel/sched/rt.c:313:5: warning: no previous prototype for 'alloc_rt_sched_group' [-Wmissing-prototypes]
313 | int alloc_rt_sched_group(struct task_group *tg, struct task_group *parent)
| ^~~~~~~~~~~~~~~~~~~~
kernel/sched/rt.c:716:6: warning: no previous prototype for 'sched_rt_bandwidth_account' [-Wmissing-prototypes]
716 | bool sched_rt_bandwidth_account(struct rt_rq *rt_rq)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
>> kernel/sched/rt.c:9:18: warning: 'max_rt_runtime' defined but not used [-Wunused-const-variable=]
9 | static const u64 max_rt_runtime = MAX_BW;
| ^~~~~~~~~~~~~~
In file included from arch/s390/include/asm/bitops.h:39,
from include/linux/bitops.h:33,
from include/linux/kernel.h:22,
from include/linux/cpumask.h:10,
from include/linux/smp.h:13,
from include/linux/sched/clock.h:5,
from kernel/sched/build_policy.c:16:
In function '__atomic_add',
inlined from '__preempt_count_add' at arch/s390/include/asm/preempt.h:52:3:
arch/s390/include/asm/atomic_ops.h:52:9: warning: array subscript 0 is outside array bounds of 'int[0]' [-Warray-bounds=]
52 | asm volatile( \
| ^~~
arch/s390/include/asm/atomic_ops.h:61:9: note: in expansion of macro '__ATOMIC_OP'
61 | __ATOMIC_OP(op_name, op_type, op_string, "\n") \
| ^~~~~~~~~~~
arch/s390/include/asm/atomic_ops.h:64:1: note: in expansion of macro '__ATOMIC_OPS'
64 | __ATOMIC_OPS(__atomic_add, int, "laa")
| ^~~~~~~~~~~~
In function '__preempt_count_add':
cc1: note: source object is likely at address zero
In function '__atomic_add',
inlined from '__preempt_count_add' at arch/s390/include/asm/preempt.h:52:3:
arch/s390/include/asm/atomic_ops.h:52:9: warning: array subscript 0 is outside array bounds of 'int[0]' [-Warray-bounds=]
52 | asm volatile( \
| ^~~
arch/s390/include/asm/atomic_ops.h:61:9: note: in expansion of macro '__ATOMIC_OP'
61 | __ATOMIC_OP(op_name, op_type, op_string, "\n") \
| ^~~~~~~~~~~
arch/s390/include/asm/atomic_ops.h:64:1: note: in expansion of macro '__ATOMIC_OPS'
64 | __ATOMIC_OPS(__atomic_add, int, "laa")
| ^~~~~~~~~~~~
In function '__preempt_count_add':
cc1: note: source object is likely at address zero
In function '__atomic_and',
inlined from 'set_preempt_need_resched' at arch/s390/include/asm/preempt.h:34:2,
inlined from 'do_idle' at kernel/sched/idle.c:315:2:
arch/s390/include/asm/atomic_ops.h:52:9: warning: array subscript 0 is outside array bounds of 'int[0]' [-Warray-bounds=]
52 | asm volatile( \
| ^~~
arch/s390/include/asm/atomic_ops.h:61:9: note: in expansion of macro '__ATOMIC_OP'
61 | __ATOMIC_OP(op_name, op_type, op_string, "\n") \
| ^~~~~~~~~~~
arch/s390/include/asm/atomic_ops.h:65:1: note: in expansion of macro '__ATOMIC_OPS'
65 | __ATOMIC_OPS(__atomic_and, int, "lan")
| ^~~~~~~~~~~~
In function 'do_idle':
cc1: note: source object is likely at address zero
In function '__atomic_and',
inlined from 'set_preempt_need_resched' at arch/s390/include/asm/preempt.h:34:2,
inlined from 'do_idle' at kernel/sched/idle.c:315:2:
arch/s390/include/asm/atomic_ops.h:52:9: warning: array subscript 0 is outside array bounds of 'int[0]' [-Warray-bounds=]
52 | asm volatile( \
| ^~~
arch/s390/include/asm/atomic_ops.h:61:9: note: in expansion of macro '__ATOMIC_OP'
61 | __ATOMIC_OP(op_name, op_type, op_string, "\n") \
| ^~~~~~~~~~~
arch/s390/include/asm/atomic_ops.h:65:1: note: in expansion of macro '__ATOMIC_OPS'
65 | __ATOMIC_OPS(__atomic_and, int, "lan")
| ^~~~~~~~~~~~
In function 'do_idle':
cc1: note: source object is likely at address zero
In function '__atomic_and',
inlined from 'set_preempt_need_resched' at arch/s390/include/asm/preempt.h:34:2,
inlined from 'play_idle_precise' at kernel/sched/idle.c:390:2:
arch/s390/include/asm/atomic_ops.h:52:9: warning: array subscript 0 is outside array bounds of 'int[0]' [-Warray-bounds=]
52 | asm volatile( \
| ^~~
arch/s390/include/asm/atomic_ops.h:61:9: note: in expansion of macro '__ATOMIC_OP'
61 | __ATOMIC_OP(op_name, op_type, op_string, "\n") \
| ^~~~~~~~~~~
arch/s390/include/asm/atomic_ops.h:65:1: note: in expansion of macro '__ATOMIC_OPS'
65 | __ATOMIC_OPS(__atomic_and, int, "lan")
| ^~~~~~~~~~~~
In function 'play_idle_precise':
cc1: note: source object is likely at address zero
In function '__atomic_and',
inlined from 'set_preempt_need_resched' at arch/s390/include/asm/preempt.h:34:2,
inlined from 'play_idle_precise' at kernel/sched/idle.c:390:2:
arch/s390/include/asm/atomic_ops.h:52:9: warning: array subscript 0 is outside array bounds of 'int[0]' [-Warray-bounds=]
52 | asm volatile( \
| ^~~
arch/s390/include/asm/atomic_ops.h:61:9: note: in expansion of macro '__ATOMIC_OP'
61 | __ATOMIC_OP(op_name, op_type, op_string, "\n") \
| ^~~~~~~~~~~
arch/s390/include/asm/atomic_ops.h:65:1: note: in expansion of macro '__ATOMIC_OPS'
65 | __ATOMIC_OPS(__atomic_and, int, "lan")
| ^~~~~~~~~~~~
In function 'play_idle_precise':
cc1: note: source object is likely at address zero
In file included from ./arch/s390/include/generated/asm/rwonce.h:1,
from include/linux/compiler.h:248,
from include/linux/build_bug.h:5,
from include/linux/container_of.h:5,
from include/linux/list.h:5,
from include/linux/smp.h:12:
In function 'preempt_count',
inlined from 'account_system_time' at kernel/sched/cputime.c:188:31:
include/asm-generic/rwonce.h:44:26: warning: array subscript 0 is outside array bounds of 'const volatile int[0]' [-Warray-bounds=]
vim +/max_rt_runtime +9 kernel/sched/rt.c
d505b8af58912a Huaixin Chang 2020-04-25 @9 static const u64 max_rt_runtime = MAX_BW;
ce0dbbbb30aee6 Clark Williams 2013-02-07 10
:::::: The code at line 9 was first introduced by commit
:::::: d505b8af58912ae1e1a211fabc9995b19bd40828 sched: Defend cfs and rt bandwidth quota against overflow
:::::: TO: Huaixin Chang <changhuaixin@linux.alibaba.com>
:::::: CC: Peter Zijlstra <peterz@infradead.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-12-22 1:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 1:22 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-22 1:31 kernel test robot
2025-06-26 7:24 kernel test robot
2025-05-21 15:57 kernel test robot
2025-04-16 13:47 kernel test robot
2025-01-03 0:22 kernel test robot
2023-12-19 7:04 kernel test robot
2023-11-12 19:38 kernel test robot
2023-10-15 11:03 kernel test robot
2023-04-30 22:24 kernel test robot
2022-11-07 17:00 kernel test robot
2022-08-06 20:19 kernel test robot
2022-05-27 17:48 kernel test robot
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=202412220957.YMZbEEtD-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhongbaisong@huawei.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
Powered by JetHome