public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [frederic-dynticks:timers/softirq-preemptible 5/6] kernel/time/timer.c:1700:3: error: call to undeclared function 'local_bh_vec_disable'; ISO C99 and later do not support implicit function declarations
Date: Tue, 1 Aug 2023 22:57:53 +0800	[thread overview]
Message-ID: <202308012245.VWA9uc8o-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git timers/softirq-preemptible
head:   c233aee141ddb78d07b2f7311be38cfc286de654
commit: e54180a8daee54a469b182cd7e753d17e52394ef [5/6] timers: Introduce soft-interruptible timers
config: arm64-randconfig-r021-20230731 (https://download.01.org/0day-ci/archive/20230801/202308012245.VWA9uc8o-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce: (https://download.01.org/0day-ci/archive/20230801/202308012245.VWA9uc8o-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/202308012245.VWA9uc8o-lkp@intel.com/

All errors (new ones prefixed by >>):

>> kernel/time/timer.c:1700:3: error: call to undeclared function 'local_bh_vec_disable'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
                   local_bh_vec_disable(1 << TIMER_SOFTIRQ);
                   ^
   kernel/time/timer.c:1700:3: note: did you mean 'local_bh_disable'?
   include/linux/bottom_half.h:18:20: note: 'local_bh_disable' declared here
   static inline void local_bh_disable(void)
                      ^
>> kernel/time/timer.c:1719:3: error: call to undeclared function 'local_bh_vec_enable'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
                   local_bh_vec_enable(1 << TIMER_SOFTIRQ);
                   ^
   kernel/time/timer.c:1719:3: note: did you mean 'local_bh_enable'?
   include/linux/bottom_half.h:31:20: note: 'local_bh_enable' declared here
   static inline void local_bh_enable(void)
                      ^
   2 errors generated.


vim +/local_bh_vec_disable +1700 kernel/time/timer.c

  1693	
  1694		if (IS_ENABLED(CONFIG_PREEMPT_RT) &&
  1695		    IS_ENABLED(CONFIG_ARCH_HAS_SOFTIRQ_DISABLED_MASK) &&
  1696		    timer->flags & TIMER_SOFTINTERRUPTIBLE)
  1697			softinterruptible = true;
  1698	
  1699		if (softinterruptible) {
> 1700			local_bh_vec_disable(1 << TIMER_SOFTIRQ);
  1701			local_bh_exit();
  1702		}
  1703	
  1704		/*
  1705		 * Couple the lock chain with the lock chain at
  1706		 * timer_delete_sync() by acquiring the lock_map around the fn()
  1707		 * call here and in timer_delete_sync().
  1708		 */
  1709		lock_map_acquire(&lockdep_map);
  1710	
  1711		trace_timer_expire_entry(timer, baseclk);
  1712		fn(timer);
  1713		trace_timer_expire_exit(timer);
  1714	
  1715		lock_map_release(&lockdep_map);
  1716	
  1717		if (softinterruptible) {
  1718			local_bh_enter();
> 1719			local_bh_vec_enable(1 << TIMER_SOFTIRQ);
  1720		}
  1721	
  1722	
  1723		if (count != preempt_count()) {
  1724			WARN_ONCE(1, "timer: %pS preempt leak: %08x -> %08x\n",
  1725				  fn, count, preempt_count());
  1726			/*
  1727			 * Restore the preempt count. That gives us a decent
  1728			 * chance to survive and extract information. If the
  1729			 * callback kept a lock held, bad luck, but not worse
  1730			 * than the BUG() we had.
  1731			 */
  1732			preempt_count_set(count);
  1733		}
  1734	}
  1735	

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

                 reply	other threads:[~2023-08-01 14:59 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=202308012245.VWA9uc8o-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=frederic@kernel.org \
    --cc=llvm@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox