All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: steven@liquorix.net
Cc: oe-kbuild-all@lists.linux.dev
Subject: [zen:7.2/prjc 118/118] kernel/sched/alt_core.c:5356:6: warning: no previous prototype for function 'rt_mutex_futex_pre_schedule'
Date: Tue, 15 Sep 2026 16:23:55 +0200	[thread overview]
Message-ID: <202609151610.HZbfQR10-lkp@intel.com> (raw)

tree:   https://github.com/zen-kernel/zen-kernel 7.2/prjc
head:   ecdb5900a34a8291a8457c0e29cca911c55dbf67
commit: ecdb5900a34a8291a8457c0e29cca911c55dbf67 [118/118] sched/alt: [Sync] b715872ef0cc futex: Provide rt_mutex_.*_schedule() equivalents for futex scheduling
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20260915/202609151610.HZbfQR10-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260915/202609151610.HZbfQR10-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/202609151610.HZbfQR10-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/sched/alt_core.c:5356:6: warning: no previous prototype for function 'rt_mutex_futex_pre_schedule' [-Wmissing-prototypes]
    5356 | void rt_mutex_futex_pre_schedule(void)
         |      ^
   kernel/sched/alt_core.c:5356:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    5356 | void rt_mutex_futex_pre_schedule(void)
         | ^
         | static 
>> kernel/sched/alt_core.c:5375:6: warning: no previous prototype for function 'rt_mutex_futex_post_schedule' [-Wmissing-prototypes]
    5375 | void rt_mutex_futex_post_schedule(void)
         |      ^
   kernel/sched/alt_core.c:5375:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    5375 | void rt_mutex_futex_post_schedule(void)
         | ^
         | static 
   kernel/sched/alt_core.c:2051:19: warning: stack frame size (2176) exceeds limit (2048) in 'select_task_rq' [-Wframe-larger-than]
    2051 | static inline int select_task_rq(struct task_struct *p, int wake_flags)
         |                   ^
   kernel/sched/alt_core.c:4703:20: warning: stack frame size (2232) exceeds limit (2048) in 'prio_balance' [-Wframe-larger-than]
    4703 | static inline void prio_balance(struct rq *rq, const int cpu)
         |                    ^
   4 warnings generated.


vim +/rt_mutex_futex_pre_schedule +5356 kernel/sched/alt_core.c

  5351	
  5352	/*
  5353	 * Used within the futex syscall context, skips sched_submit_work() because none
  5354	 * its work will be done. Asserts ensure that it is indeed the case.
  5355	 */
> 5356	void rt_mutex_futex_pre_schedule(void)
  5357	{
  5358		lockdep_assert(!(current->flags & (PF_WQ_WORKER | PF_IO_WORKER)));
  5359		lockdep_assert(!current->plug);
  5360		lockdep_assert(!fetch_and_set(current->sched_rt_mutex, 1));
  5361	}
  5362	
  5363	void rt_mutex_schedule(void)
  5364	{
  5365		lockdep_assert(current->sched_rt_mutex);
  5366		__schedule_loop(SM_NONE);
  5367	}
  5368	
  5369	void rt_mutex_post_schedule(void)
  5370	{
  5371		sched_update_worker(current);
  5372		lockdep_assert(fetch_and_set(current->sched_rt_mutex, 0));
  5373	}
  5374	
> 5375	void rt_mutex_futex_post_schedule(void)
  5376	{
  5377		lockdep_assert(fetch_and_set(current->sched_rt_mutex, 0));
  5378	}
  5379	

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

                 reply	other threads:[~2026-09-15 14:24 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=202609151610.HZbfQR10-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=steven@liquorix.net \
    /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.