All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: aubrey.li@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [anolis-intel-cloud:devel-6.6 272/272] kernel/sched/fair.c:9774:69: warning: 'struct lb_env' declared inside parameter list will not be visible outside of this definition or declaration
Date: Sun, 30 Aug 2026 10:09:50 +0800	[thread overview]
Message-ID: <202608301009.JSDb3U23-lkp@intel.com> (raw)

Hi Cruz,

FYI, the error/warning still remains.

tree:   https://gitee.com/anolis/intel-cloud-kernel.git devel-6.6
head:   41cf029dd674935312f07b9ff27127f205008195
commit: 64194706630f8c78feb5fb01b6d046aa4aab66df [272/272] anolis: sched: add tunables for expeller and expellee load balance
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20260830/202608301009.JSDb3U23-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260830/202608301009.JSDb3U23-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/202608301009.JSDb3U23-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from kernel/sched/fair.c:56:
   kernel/sched/sched.h:1859:54: warning: 'struct cgroup_taskset' declared inside parameter list will not be visible outside of this definition or declaration
    1859 | static inline void sched_core_identity_attach(struct cgroup_taskset *tset) { }
         |                                                      ^~~~~~~~~~~~~~
>> kernel/sched/fair.c:9774:69: warning: 'struct lb_env' declared inside parameter list will not be visible outside of this definition or declaration
    9774 | static inline int id_can_migrate_task(struct task_struct *p, struct lb_env *env)
         |                                                                     ^~~~~~


vim +9774 kernel/sched/fair.c

  9740	
  9741	#else
  9742	static inline void push_expellee(struct rq *rq) { }
  9743	#endif
  9744	static int id_can_migrate_task(struct task_struct *p, struct lb_env *env)
  9745	{
  9746		struct rq *src_rq = env->src_rq;
  9747		struct rq *dst_rq = env->dst_rq;
  9748	
  9749		if (!id_expeller_share_core() && env->id_need_redo && task_is_expeller(p) &&
  9750		    rq_on_expel_by_smt_expeller(dst_rq))
  9751			goto bad_dst;
  9752		if ((!sched_feat(ID_SMT_EXPEL) || !task_is_expellee(p)) &&
  9753		    (!sched_feat(ID_ABSOLUTE_EXPEL) || !task_is_idle(p)))
  9754			return -1;
  9755		/* Do not migrate expellee task to CPU on expel */
  9756		if (should_expel_se(dst_rq, &p->se))
  9757			goto bad_dst;
  9758		if (sched_feat(ID_EXPELLEE_NEVER_HOT))
  9759			goto good_dst;
  9760		if (!should_expel_se(src_rq, &p->se))
  9761			return -1;
  9762		if (!sched_feat(ID_RESCUE_EXPELLEE))
  9763			return -1;
  9764	good_dst:
  9765		schedstat_inc(p->stats.nr_forced_migrations);
  9766		return 1;
  9767	bad_dst:
  9768		schedstat_inc(p->stats.nr_failed_migrations_id);
  9769		return 0;
  9770	}
  9771	#else
  9772	static inline void update_rq_on_expel(struct rq *rq) { }
  9773	static inline void push_expellee(struct rq *rq) { }
> 9774	static inline int id_can_migrate_task(struct task_struct *p, struct lb_env *env)
  9775	{
  9776		return -1;
  9777	}
  9778	#endif
  9779	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-08-30  2:10 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=202608301009.JSDb3U23-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aubrey.li@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.