From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v15 37/43] dept: assign unique dept_key to each distinct wait_for_completion() caller
Date: Wed, 14 May 2025 18:16:34 +0800 [thread overview]
Message-ID: <202505141759.avvm2GOf-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250513100730.12664-38-byungchul@sk.com>
References: <20250513100730.12664-38-byungchul@sk.com>
TO: Byungchul Park <byungchul@sk.com>
TO: linux-kernel@vger.kernel.org
CC: kernel_team@skhynix.com
CC: torvalds@linux-foundation.org
CC: damien.lemoal@opensource.wdc.com
CC: linux-ide@vger.kernel.org
CC: adilger.kernel@dilger.ca
CC: linux-ext4@vger.kernel.org
CC: mingo@redhat.com
CC: peterz@infradead.org
CC: will@kernel.org
CC: tglx@linutronix.de
CC: rostedt@goodmis.org
CC: joel@joelfernandes.org
CC: sashal@kernel.org
CC: daniel.vetter@ffwll.ch
CC: duyuyang@gmail.com
CC: johannes.berg@intel.com
CC: tj@kernel.org
CC: tytso@mit.edu
CC: willy@infradead.org
CC: david@fromorbit.com
CC: amir73il@gmail.com
CC: gregkh@linuxfoundation.org
CC: kernel-team@lge.com
CC: linux-mm@kvack.org
CC: akpm@linux-foundation.org
CC: mhocko@kernel.org
CC: minchan@kernel.org
CC: hannes@cmpxchg.org
CC: vdavydov.dev@gmail.com
Hi Byungchul,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3]
url: https://github.com/intel-lab-lkp/linux/commits/Byungchul-Park/llist-move-llist_-head-node-definition-to-types-h/20250513-181346
base: 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3
patch link: https://lore.kernel.org/r/20250513100730.12664-38-byungchul%40sk.com
patch subject: [PATCH v15 37/43] dept: assign unique dept_key to each distinct wait_for_completion() caller
:::::: branch date: 24 hours ago
:::::: commit date: 24 hours ago
config: loongarch-randconfig-r071-20250514 (https://download.01.org/0day-ci/archive/20250514/202505141759.avvm2GOf-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.2.0
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202505141759.avvm2GOf-lkp@intel.com/
smatch warnings:
kernel/sched/completion.c:167 __wait_for_completion_timeout() error: 'wait_for_common()' returns negative and '__fake_return_0x7fd58a360280' is unsigned
vim +167 kernel/sched/completion.c
b8a216269ec0ce Peter Zijlstra 2013-10-04 151
b8a216269ec0ce Peter Zijlstra 2013-10-04 152 /**
203be867bd3b2b Byungchul Park 2025-05-13 153 * __wait_for_completion_timeout: - waits for completion of a task (w/timeout)
b8a216269ec0ce Peter Zijlstra 2013-10-04 154 * @x: holds the state of this particular completion
b8a216269ec0ce Peter Zijlstra 2013-10-04 155 * @timeout: timeout value in jiffies
b8a216269ec0ce Peter Zijlstra 2013-10-04 156 *
b8a216269ec0ce Peter Zijlstra 2013-10-04 157 * This waits for either a completion of a specific task to be signaled or for a
b8a216269ec0ce Peter Zijlstra 2013-10-04 158 * specified timeout to expire. The timeout is in jiffies. It is not
b8a216269ec0ce Peter Zijlstra 2013-10-04 159 * interruptible.
b8a216269ec0ce Peter Zijlstra 2013-10-04 160 *
b8a216269ec0ce Peter Zijlstra 2013-10-04 161 * Return: 0 if timed out, and positive (at least 1, or number of jiffies left
b8a216269ec0ce Peter Zijlstra 2013-10-04 162 * till timeout) if completed.
b8a216269ec0ce Peter Zijlstra 2013-10-04 163 */
b8a216269ec0ce Peter Zijlstra 2013-10-04 164 unsigned long __sched
203be867bd3b2b Byungchul Park 2025-05-13 165 __wait_for_completion_timeout(struct completion *x, unsigned long timeout)
b8a216269ec0ce Peter Zijlstra 2013-10-04 166 {
b8a216269ec0ce Peter Zijlstra 2013-10-04 @167 return wait_for_common(x, timeout, TASK_UNINTERRUPTIBLE);
b8a216269ec0ce Peter Zijlstra 2013-10-04 168 }
203be867bd3b2b Byungchul Park 2025-05-13 169 EXPORT_SYMBOL(__wait_for_completion_timeout);
b8a216269ec0ce Peter Zijlstra 2013-10-04 170
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-05-14 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 10:16 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-13 10:06 [PATCH v15 00/43] DEPT(DEPendency Tracker) Byungchul Park
2025-05-13 10:07 ` [PATCH v15 37/43] dept: assign unique dept_key to each distinct wait_for_completion() caller Byungchul Park
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=202505141759.avvm2GOf-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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 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.