From: kernel test robot <lkp@intel.com>
To: Byungchul Park <byungchul@sk.com>, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
kernel_team@skhynix.com, torvalds@linux-foundation.org,
damien.lemoal@opensource.wdc.com, linux-ide@vger.kernel.org,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
mingo@redhat.com, peterz@infradead.org, will@kernel.org,
tglx@linutronix.de, rostedt@goodmis.org, joel@joelfernandes.org,
sashal@kernel.org, daniel.vetter@ffwll.ch, duyuyang@gmail.com,
johannes.berg@intel.com, tj@kernel.org, tytso@mit.edu,
willy@infradead.org, david@fromorbit.com, amir73il@gmail.com,
gregkh@linuxfoundation.org, kernel-team@lge.com,
linux-mm@kvack.org, akpm@linux-foundation.org, mhocko@kernel.org,
minchan@kernel.org, hannes@cmpxchg.org, vdavydov.dev@gmail.com
Subject: Re: [PATCH v15 33/43] dept: assign unique dept_key to each distinct dma fence caller
Date: Wed, 14 May 2025 06:49:42 +0800 [thread overview]
Message-ID: <202505140631.FOWO8B5L-lkp@intel.com> (raw)
In-Reply-To: <20250513100730.12664-34-byungchul@sk.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-34-byungchul%40sk.com
patch subject: [PATCH v15 33/43] dept: assign unique dept_key to each distinct dma fence caller
config: arm-randconfig-002-20250514 (https://download.01.org/0day-ci/archive/20250514/202505140631.FOWO8B5L-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250514/202505140631.FOWO8B5L-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/202505140631.FOWO8B5L-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/dma-buf/dma-fence.c:503: warning: expecting prototype for dma_fence_wait_timeout(). Prototype was for __dma_fence_wait_timeout() instead
>> drivers/dma-buf/dma-fence.c:763: warning: expecting prototype for dma_fence_default_wait(). Prototype was for __dma_fence_default_wait() instead
>> drivers/dma-buf/dma-fence.c:853: warning: expecting prototype for dma_fence_wait_any_timeout(). Prototype was for __dma_fence_wait_any_timeout() instead
vim +503 drivers/dma-buf/dma-fence.c
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 482
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 483 /**
f54d1867005c33 drivers/dma-buf/dma-fence.c Chris Wilson 2016-10-25 484 * dma_fence_wait_timeout - sleep until the fence gets signaled
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 485 * or until timeout elapses
4dd3cdb281f7a3 drivers/dma-buf/dma-fence.c Simona Vetter 2018-07-04 486 * @fence: the fence to wait on
4dd3cdb281f7a3 drivers/dma-buf/dma-fence.c Simona Vetter 2018-07-04 487 * @intr: if true, do an interruptible wait
4dd3cdb281f7a3 drivers/dma-buf/dma-fence.c Simona Vetter 2018-07-04 488 * @timeout: timeout value in jiffies, or MAX_SCHEDULE_TIMEOUT
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 489 *
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 490 * Returns -ERESTARTSYS if interrupted, 0 if the wait timed out, or the
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 491 * remaining timeout in jiffies on success. Other error values may be
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 492 * returned on custom implementations.
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 493 *
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 494 * Performs a synchronous wait on this fence. It is assumed the caller
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 495 * directly or indirectly (buf-mgr between reservation and committing)
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 496 * holds a reference to the fence, otherwise the fence might be
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 497 * freed before return, resulting in undefined behavior.
4dd3cdb281f7a3 drivers/dma-buf/dma-fence.c Simona Vetter 2018-07-04 498 *
4dd3cdb281f7a3 drivers/dma-buf/dma-fence.c Simona Vetter 2018-07-04 499 * See also dma_fence_wait() and dma_fence_wait_any_timeout().
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 500 */
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 501 signed long
15fe92c1e1cf69 drivers/dma-buf/dma-fence.c Byungchul Park 2025-05-13 502 __dma_fence_wait_timeout(struct dma_fence *fence, bool intr, signed long timeout)
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 @503 {
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 504 signed long ret;
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 505
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 506 if (WARN_ON(timeout < 0))
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 507 return -EINVAL;
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 508
ef8255506f6682 drivers/dma-buf/dma-fence.c Simona Vetter 2020-05-19 509 might_sleep();
ef8255506f6682 drivers/dma-buf/dma-fence.c Simona Vetter 2020-05-19 510
5fbff813a4a328 drivers/dma-buf/dma-fence.c Simona Vetter 2020-07-07 511 __dma_fence_might_wait();
5fbff813a4a328 drivers/dma-buf/dma-fence.c Simona Vetter 2020-07-07 512
b96fb1e724ae68 drivers/dma-buf/dma-fence.c Arvind Yadav 2022-09-14 513 dma_fence_enable_sw_signaling(fence);
b96fb1e724ae68 drivers/dma-buf/dma-fence.c Arvind Yadav 2022-09-14 514
f54d1867005c33 drivers/dma-buf/dma-fence.c Chris Wilson 2016-10-25 515 trace_dma_fence_wait_start(fence);
418cc6ca06071e drivers/dma-buf/dma-fence.c Simona Vetter 2018-05-03 516 if (fence->ops->wait)
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 517 ret = fence->ops->wait(fence, intr, timeout);
418cc6ca06071e drivers/dma-buf/dma-fence.c Simona Vetter 2018-05-03 518 else
418cc6ca06071e drivers/dma-buf/dma-fence.c Simona Vetter 2018-05-03 519 ret = dma_fence_default_wait(fence, intr, timeout);
f54d1867005c33 drivers/dma-buf/dma-fence.c Chris Wilson 2016-10-25 520 trace_dma_fence_wait_end(fence);
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 521 return ret;
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 522 }
15fe92c1e1cf69 drivers/dma-buf/dma-fence.c Byungchul Park 2025-05-13 523 EXPORT_SYMBOL(__dma_fence_wait_timeout);
e941759c74a44d drivers/dma-buf/fence.c Maarten Lankhorst 2014-07-01 524
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2025-05-13 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250513100730.12664-34-byungchul@sk.com>
2025-05-13 22:49 ` kernel test robot [this message]
2025-05-16 8:07 ` [PATCH v15 33/43] dept: assign unique dept_key to each distinct dma fence caller Byungchul Park
2025-05-14 12:46 ` kernel test robot
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=202505140631.FOWO8B5L-lkp@intel.com \
--to=lkp@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=byungchul@sk.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.vetter@ffwll.ch \
--cc=david@fromorbit.com \
--cc=duyuyang@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=joel@joelfernandes.org \
--cc=johannes.berg@intel.com \
--cc=kernel-team@lge.com \
--cc=kernel_team@skhynix.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vdavydov.dev@gmail.com \
--cc=will@kernel.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox