llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cx19970 <cx19970@qq.com>,
	mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
	linux-kernel@vger.kernel.org, cx19970 <cx19970@qq.com>
Subject: Re: [PATCH] BUG: sysrq: Reset the watchdog during the polling of sysrq-t processing tasks
Date: Mon, 17 Nov 2025 16:02:24 +0800	[thread overview]
Message-ID: <202511171548.yY6PHme5-lkp@intel.com> (raw)
In-Reply-To: <tencent_B7DDA306E3B6A8CDF3195E4C083C9BD37E07@qq.com>

Hi cx19970,

kernel test robot noticed the following build errors:

[auto build test ERROR on tip/sched/core]
[also build test ERROR on linus/master v6.18-rc6 next-20251114]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/cx19970/BUG-sysrq-Reset-the-watchdog-during-the-polling-of-sysrq-t-processing-tasks/20251117-130012
base:   tip/sched/core
patch link:    https://lore.kernel.org/r/tencent_B7DDA306E3B6A8CDF3195E4C083C9BD37E07%40qq.com
patch subject: [PATCH] BUG: sysrq: Reset the watchdog during the polling of sysrq-t processing tasks
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20251117/202511171548.yY6PHme5-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 0bba1e76581bad04e7d7f09f5115ae5e2989e0d9)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251117/202511171548.yY6PHme5-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/202511171548.yY6PHme5-lkp@intel.com/

All errors (new ones prefixed by >>):

>> kernel/sched/fair.c:13940:3: error: call to undeclared function 'touch_nmi_watchdog'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    13940 |                 touch_nmi_watchdog();
          |                 ^
>> kernel/sched/fair.c:13941:3: error: call to undeclared function 'touch_all_softlockup_watchdogs'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    13941 |                 touch_all_softlockup_watchdogs();
          |                 ^
   2 errors generated.
--
   In file included from kernel/sched/build_policy.c:52:
>> kernel/sched/rt.c:2941:3: error: call to undeclared function 'touch_nmi_watchdog'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    2941 |                 touch_nmi_watchdog();
         |                 ^
>> kernel/sched/rt.c:2942:3: error: call to undeclared function 'touch_all_softlockup_watchdogs'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    2942 |                 touch_all_softlockup_watchdogs();
         |                 ^
   2 errors generated.


vim +/touch_nmi_watchdog +13940 kernel/sched/fair.c

 13933	
 13934	void print_cfs_stats(struct seq_file *m, int cpu)
 13935	{
 13936		struct cfs_rq *cfs_rq, *pos;
 13937	
 13938		rcu_read_lock();
 13939		for_each_leaf_cfs_rq_safe(cpu_rq(cpu), cfs_rq, pos) {
 13940			touch_nmi_watchdog();
 13941			touch_all_softlockup_watchdogs();
 13942			print_cfs_rq(m, cpu, cfs_rq);
 13943		}
 13944		rcu_read_unlock();
 13945	}
 13946	

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

           reply	other threads:[~2025-11-17  8:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <tencent_B7DDA306E3B6A8CDF3195E4C083C9BD37E07@qq.com>]

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=202511171548.yY6PHme5-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bsegall@google.com \
    --cc=cx19970@qq.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).