From: sashiko-bot@kernel.org
To: "Tejun Heo" <tj@kernel.org>
Cc: sched-ext@lists.linux.dev
Subject: Re: [PATCH 02/12] sched_ext: Make several ext.c helpers available outside ext.c
Date: Sat, 01 Aug 2026 08:58:08 +0000 [thread overview]
Message-ID: <20260801085808.AEE2B1F00AC4@smtp.kernel.org> (raw)
In-Reply-To: <20260801085150.2697653-3-tj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Unconditional definition of `scx_sched_all` lacks a prototype when `CONFIG_EXT_SUB_SCHED` is disabled, causing a build warning.
--
--- Patch [2]: [PATCH 02/12] sched_ext: Make several ext.c helpers available outside ext.c ---
commit 2fbc86143bb66368e04e606cb09e7ffe2b987b3d
Author: Tejun Heo <tj@kernel.org>
sched_ext: Make several ext.c helpers available outside ext.c
This commit exposes several helper functions and the scx_sched_all list
by removing their static keywords and adding declarations in internal.h.
This allows them to be utilized outside of ext.c.
> --- a/kernel/sched/ext/ext.c
> +++ b/kernel/sched/ext/ext.c
> @@ -38,7 +38,7 @@ struct scx_sched __rcu *scx_root;
> * All scheds, writers must hold both scx_enable_mutex and scx_sched_lock.
> * Readers can hold either or rcu_read_lock().
> */
> -static LIST_HEAD(scx_sched_all);
> +LIST_HEAD(scx_sched_all);
[ ... ]
> --- a/kernel/sched/ext/internal.h
> +++ b/kernel/sched/ext/internal.h
> @@ -2014,6 +2021,7 @@ extern bool scx_cgroup_enabled;
> #ifdef CONFIG_EXT_SUB_SCHED
> extern const struct rhashtable_params scx_sched_hash_params;
> extern struct rhashtable scx_sched_hash;
> +extern struct list_head scx_sched_all;
[Severity: Low]
Will this trigger a missing prototype warning when CONFIG_EXT_SUB_SCHED is
disabled?
Because scx_sched_all is defined unconditionally in ext.c, building the
kernel without CONFIG_EXT_SUB_SCHED hides this extern declaration in
internal.h from the compiler.
Should this declaration be moved outside of the ifdef block to prevent
compiler or sparse warnings?
> extern struct scx_sched *scx_enabling_sub_sched;
> #endif
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260801085150.2697653-1-tj@kernel.org?part=2
next prev parent reply other threads:[~2026-08-01 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 8:51 [PATCHSET sched_ext/for-7.3] sched_ext: Bandwidth-limited rescue execution for stranded tasks Tejun Heo
2026-08-01 8:51 ` [PATCH 01/12] sched_ext: Rename scx_local_or_reject_dsq() to scx_resolve_local_dsq() Tejun Heo
2026-08-01 8:51 ` [PATCH 02/12] sched_ext: Make several ext.c helpers available outside ext.c Tejun Heo
2026-08-01 8:58 ` sashiko-bot [this message]
2026-08-01 8:51 ` [PATCH 03/12] sched_ext: Factor out __scx_bpf_now() Tejun Heo
2026-08-01 8:51 ` [PATCH 04/12] sched_ext: Reject internal enq_flags in the dsq move kfuncs Tejun Heo
2026-08-01 8:51 ` [PATCH 05/12] sched_ext: Make SCX_ENQ_IGNORE_CAPS waive the preemption cap too Tejun Heo
2026-08-01 8:51 ` [PATCH 06/12] sched_ext: Synchronize slice and dsq_vtime writes Tejun Heo
2026-08-01 8:51 ` [PATCH 07/12] sched_ext: Add SCX_TASK_PROTECTED Tejun Heo
2026-08-01 8:51 ` [PATCH 08/12] sched_ext: Add bandwidth-limited rescue execution for stranded tasks Tejun Heo
2026-08-01 8:51 ` [PATCH 09/12] sched_ext: Eject the top rescue consumer on overload Tejun Heo
2026-08-01 9:11 ` sashiko-bot
2026-08-01 8:51 ` [PATCH 10/12] sched_ext: Sync tools autogen enum headers Tejun Heo
2026-08-01 8:51 ` [PATCH 11/12] sched_ext: scx_qmap - Idle-check pinned tasks before direct dispatch Tejun Heo
2026-08-01 9:06 ` sashiko-bot
2026-08-01 8:51 ` [PATCH 12/12] sched_ext: scx_qmap - Add rescue support Tejun Heo
2026-08-01 9:06 ` sashiko-bot
2026-08-02 19:51 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2026-08-02 21:54 [PATCHSET v2 sched_ext/for-7.3] sched_ext: Bandwidth-limited rescue execution for stranded tasks Tejun Heo
2026-08-02 21:54 ` [PATCH 02/12] sched_ext: Make several ext.c helpers available outside ext.c Tejun Heo
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=20260801085808.AEE2B1F00AC4@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
/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