All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, Thomas Gleixner <tglx@kernel.org>
Subject: [tglx-devel:sched/hrtick 35/48] kernel/entry/common.c:53:30: error: too many arguments to function 'rseq_grant_slice_extension'
Date: Tue, 24 Feb 2026 21:13:51 +0800	[thread overview]
Message-ID: <202602242106.dMfiUf6D-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git sched/hrtick
head:   27cd0d3a6b3db913813a2ead85957bf4dce21e04
commit: cfff40a7c0b95b3942ae221617bb5f4b09994f19 [35/48] entry: Prepare for deferred hrtimer rearming
config: x86_64-buildonly-randconfig-006-20260224 (https://download.01.org/0day-ci/archive/20260224/202602242106.dMfiUf6D-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260224/202602242106.dMfiUf6D-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/202602242106.dMfiUf6D-lkp@intel.com/

All errors (new ones prefixed by >>):

   kernel/entry/common.c: In function '__exit_to_user_mode_loop':
>> kernel/entry/common.c:53:30: error: too many arguments to function 'rseq_grant_slice_extension'
      53 |                         if (!rseq_grant_slice_extension(ti_work, TIF_SLICE_EXT_DENY))
         |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~
   In file included from include/linux/irq-entry-common.h:8,
                    from kernel/entry/common.c:3:
   include/linux/rseq_entry.h:791:20: note: declared here
     791 | static inline bool rseq_grant_slice_extension(bool work_pending) { return false; }
         |                    ^~~~~~~~~~~~~~~~~~~~~~~~~~


vim +/rseq_grant_slice_extension +53 kernel/entry/common.c

    40	
    41	static __always_inline unsigned long __exit_to_user_mode_loop(struct pt_regs *regs,
    42								      unsigned long ti_work)
    43	{
    44		/*
    45		 * Before returning to user space ensure that all pending work
    46		 * items have been completed.
    47		 */
    48		while (ti_work & EXIT_TO_USER_MODE_WORK_LOOP) {
    49	
    50			local_irq_enable_exit_to_user(ti_work);
    51	
    52			if (ti_work & (_TIF_NEED_RESCHED | _TIF_NEED_RESCHED_LAZY)) {
  > 53				if (!rseq_grant_slice_extension(ti_work, TIF_SLICE_EXT_DENY))
    54					schedule();
    55			}
    56	
    57			if (ti_work & _TIF_UPROBE)
    58				uprobe_notify_resume(regs);
    59	
    60			if (ti_work & _TIF_PATCH_PENDING)
    61				klp_update_patch_state(current);
    62	
    63			if (ti_work & (_TIF_SIGPENDING | _TIF_NOTIFY_SIGNAL))
    64				arch_do_signal_or_restart(regs);
    65	
    66			if (ti_work & _TIF_NOTIFY_RESUME)
    67				resume_user_mode_work(regs);
    68	
    69			/* Architecture specific TIF work */
    70			arch_exit_to_user_mode_work(regs, ti_work);
    71	
    72			/*
    73			 * Disable interrupts and reevaluate the work flags as they
    74			 * might have changed while interrupts and preemption was
    75			 * enabled above.
    76			 */
    77			local_irq_disable_exit_to_user();
    78	
    79			/* Check if any of the above work has queued a deferred wakeup */
    80			tick_nohz_user_enter_prepare();
    81	
    82			ti_work = read_thread_flags();
    83		}
    84	
    85		/* Return the latest work state for arch_exit_to_user_mode() */
    86		return ti_work;
    87	}
    88	

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

                 reply	other threads:[~2026-02-24 13:14 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=202602242106.dMfiUf6D-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=tglx@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 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.