From: kernel test robot <lkp@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>,
akpm@linux-foundation.org, lance.yang@linux.dev,
mhiramat@kernel.org, pmladek@suse.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
david.laight.linux@gmail.com, atomlin@atomlin.com,
neelx@suse.com, sean@ashe.io, chjohnst@gmail.com, steve@abita.co,
mproche@gmail.com, nick.lange@gmail.com
Subject: Re: [PATCH v5] hung_task: Deduplicate identical hang reports using explicit blocker tracking
Date: Wed, 5 Aug 2026 05:41:02 +0800 [thread overview]
Message-ID: <202608050541.aDhk6r1x-lkp@intel.com> (raw)
In-Reply-To: <20260712202100.123934-1-atomlin@atomlin.com>
Hi Aaron,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on tip/sched/core linus/master kees/for-next/execve v7.2-rc6 next-20260804]
[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/Aaron-Tomlin/hung_task-Deduplicate-identical-hang-reports-using-explicit-blocker-tracking/20260804-194519
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20260712202100.123934-1-atomlin%40atomlin.com
patch subject: [PATCH v5] hung_task: Deduplicate identical hang reports using explicit blocker tracking
config: openrisc-randconfig-r071-20260805 (https://download.01.org/0day-ci/archive/20260805/202608050541.aDhk6r1x-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 12.5.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260805/202608050541.aDhk6r1x-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/202608050541.aDhk6r1x-lkp@intel.com/
All warnings (new ones prefixed by >>):
kernel/hung_task.c: In function 'check_hung_uninterruptible_tasks':
>> kernel/hung_task.c:337:14: warning: variable 'scan_completed' set but not used [-Wunused-but-set-variable]
337 | bool scan_completed = false;
| ^~~~~~~~~~~~~~
vim +/scan_completed +337 kernel/hung_task.c
323
324 /*
325 * Check whether a TASK_UNINTERRUPTIBLE does not get woken up for
326 * a really long time. If that happens, print out a warning.
327 */
328 static void check_hung_uninterruptible_tasks(unsigned long timeout)
329 {
330 int max_count = sysctl_hung_task_check_count;
331 unsigned long last_break = jiffies;
332 struct task_struct *g, *t;
333 unsigned long this_round_count;
334 int need_warning = sysctl_hung_task_warnings;
335 unsigned long si_mask = hung_task_si_mask;
336 unsigned int skip_show_task;
> 337 bool scan_completed = false;
338 #ifdef CONFIG_DETECT_HUNG_TASK_BLOCKER
339 unsigned long blocker;
340 static int warnings_reset_value;
341 unsigned long seen_blockers_mask = 0;
342 #endif
343
344 /*
345 * If the system crashed already then all bets are off,
346 * do not report extra hung tasks:
347 */
348 if (test_taint(TAINT_DIE) || did_panic)
349 return;
350
351 this_round_count = 0;
352 rcu_read_lock();
353 for_each_process_thread(g, t) {
354 if (!max_count--)
355 goto unlock;
356 if (time_after(jiffies, last_break + HUNG_TASK_LOCK_BREAK)) {
357 if (!rcu_lock_break(g, t))
358 goto unlock;
359 last_break = jiffies;
360 }
361
362 if (task_is_hung(t, timeout)) {
363 skip_show_task = t->hung_task_reported;
364 /*
365 * Increment the global counter so that userspace could
366 * start migrating tasks ASAP. But count the current
367 * round separately because userspace could reset
368 * the global counter at any time.
369 */
370 atomic_long_inc(&sysctl_hung_task_detect_count);
371 this_round_count++;
372
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-04 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 20:21 Aaron Tomlin
2026-07-13 0:08 ` Aaron Tomlin
2026-08-04 21:41 ` kernel test robot [this message]
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=202608050541.aDhk6r1x-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=chjohnst@gmail.com \
--cc=david.laight.linux@gmail.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mproche@gmail.com \
--cc=neelx@suse.com \
--cc=nick.lange@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmladek@suse.com \
--cc=sean@ashe.io \
--cc=steve@abita.co \
/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
all inboxes | Powered by JetHome®