From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 59643C5AD7B for ; Sat, 21 Feb 2026 15:29:16 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 8E15710E0A0; Sat, 21 Feb 2026 15:29:15 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="nZJVS4Ct"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.16]) by gabe.freedesktop.org (Postfix) with ESMTPS id 1629610E0C5 for ; Sat, 21 Feb 2026 15:29:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1771687754; x=1803223754; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=4JjL0l+nLorUxDyMz8O1wmqKirNzDbDtAXWdXi0Ls+U=; b=nZJVS4CtTQ551KSDmChha+hE2HdPxxl6wjPzB2xFxY3E7qDB4XK2NVAx PvBv9ty95xmQ4c5djvdlVCuIR6Lx+UFoGl7amE2lTNDtXsZw8CbZbmy+y 4WM0MKj4/LmY7JJm6+FuQSTVlQihrEe13SrPSITJ/KPGPxLl2238SoGH3 7Xu5RjiDbS7rmelHJ0Evlo89VJ2SEsD/ba7YcNIo3bRCPIgiZ9hJr2RgJ +RpjS78iiBdEFfG0G7L7aF7LKEr28UELBiPyXiFVUPiduaoYwBBUGryFQ seqjFJLVJFROPQf1E8BZK2zuhqV06kdCNiocSVIJkwPCEEWOBvcvIpd29 w==; X-CSE-ConnectionGUID: rLl2zdsFSOm/egyyWZK4+Q== X-CSE-MsgGUID: jXRZ27irTvKO1miq7BXipg== X-IronPort-AV: E=McAfee;i="6800,10657,11708"; a="60324291" X-IronPort-AV: E=Sophos;i="6.21,304,1763452800"; d="scan'208";a="60324291" Received: from fmviesa002.fm.intel.com ([10.60.135.142]) by fmvoesa110.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2026 07:29:13 -0800 X-CSE-ConnectionGUID: nWVBhHZ8Q/2hQ5l00AfygQ== X-CSE-MsgGUID: 5d11ktmXSq2b4fYgGqpTmw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,304,1763452800"; d="scan'208";a="238074591" Received: from lkp-server01.sh.intel.com (HELO 765f4a05e27f) ([10.239.97.150]) by fmviesa002.fm.intel.com with ESMTP; 21 Feb 2026 07:29:11 -0800 Received: from kbuild by 765f4a05e27f with local (Exim 4.98.2) (envelope-from ) id 1vtour-0000000150W-29yC; Sat, 21 Feb 2026 15:29:09 +0000 Date: Sat, 21 Feb 2026 23:28:50 +0800 From: kernel test robot To: Christian =?iso-8859-1?Q?K=F6nig?= , phasta@mailbox.org, matthew.brost@intel.com, sumit.semwal@linaro.org Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org Subject: Re: [PATCH 2/8] dma-buf: detach fence ops on signal v2 Message-ID: <202602212322.qKZcoRK3-lkp@intel.com> References: <20260219160822.1529-3-christian.koenig@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260219160822.1529-3-christian.koenig@amd.com> X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Hi Christian, kernel test robot noticed the following build warnings: [auto build test WARNING on drm-misc/drm-misc-next] [cannot apply to drm-i915/for-linux-next drm-i915/for-linux-next-fixes drm-xe/drm-xe-next linus/master v6.19 next-20260220] [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/Christian-K-nig/dma-buf-detach-fence-ops-on-signal-v2/20260220-010804 base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next patch link: https://lore.kernel.org/r/20260219160822.1529-3-christian.koenig%40amd.com patch subject: [PATCH 2/8] dma-buf: detach fence ops on signal v2 config: hexagon-randconfig-r121-20260221 (https://download.01.org/0day-ci/archive/20260221/202602212322.qKZcoRK3-lkp@intel.com/config) compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project e86750b29fa0ff207cd43213d66dabe565417638) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260221/202602212322.qKZcoRK3-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 | Closes: https://lore.kernel.org/oe-kbuild-all/202602212322.qKZcoRK3-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) drivers/dma-buf/dma-fence.c:1051:38: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected char const [noderef] __rcu *timeline @@ got char * @@ drivers/dma-buf/dma-fence.c:1051:38: sparse: expected char const [noderef] __rcu *timeline drivers/dma-buf/dma-fence.c:1051:38: sparse: got char * drivers/dma-buf/dma-fence.c:1052:36: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected char const [noderef] __rcu *driver @@ got char * @@ drivers/dma-buf/dma-fence.c:1052:36: sparse: expected char const [noderef] __rcu *driver drivers/dma-buf/dma-fence.c:1052:36: sparse: got char * drivers/dma-buf/dma-fence.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/dma_fence.h): include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression >> drivers/dma-buf/dma-fence.c:379:19: sparse: sparse: dereference of noderef expression drivers/dma-buf/dma-fence.c:379:43: sparse: sparse: dereference of noderef expression vim +379 drivers/dma-buf/dma-fence.c 345 346 347 /** 348 * dma_fence_signal_timestamp_locked - signal completion of a fence 349 * @fence: the fence to signal 350 * @timestamp: fence signal timestamp in kernel's CLOCK_MONOTONIC time domain 351 * 352 * Signal completion for software callbacks on a fence, this will unblock 353 * dma_fence_wait() calls and run all the callbacks added with 354 * dma_fence_add_callback(). Can be called multiple times, but since a fence 355 * can only go from the unsignaled to the signaled state and not back, it will 356 * only be effective the first time. Set the timestamp provided as the fence 357 * signal timestamp. 358 * 359 * Unlike dma_fence_signal_timestamp(), this function must be called with 360 * &dma_fence.lock held. 361 */ 362 void dma_fence_signal_timestamp_locked(struct dma_fence *fence, 363 ktime_t timestamp) 364 { 365 struct dma_fence_cb *cur, *tmp; 366 struct list_head cb_list; 367 368 lockdep_assert_held(fence->lock); 369 370 if (unlikely(test_and_set_bit(DMA_FENCE_FLAG_SIGNALED_BIT, 371 &fence->flags))) 372 return; 373 374 /* 375 * When neither a release nor a wait operation is specified set the ops 376 * pointer to NULL to allow the fence structure to become independent 377 * from who originally issued it. 378 */ > 379 if (!fence->ops->release && !fence->ops->wait) 380 RCU_INIT_POINTER(fence->ops, NULL); 381 382 /* Stash the cb_list before replacing it with the timestamp */ 383 list_replace(&fence->cb_list, &cb_list); 384 385 fence->timestamp = timestamp; 386 set_bit(DMA_FENCE_FLAG_TIMESTAMP_BIT, &fence->flags); 387 trace_dma_fence_signaled(fence); 388 389 list_for_each_entry_safe(cur, tmp, &cb_list, node) { 390 INIT_LIST_HEAD(&cur->node); 391 cur->func(fence, cur); 392 } 393 } 394 EXPORT_SYMBOL(dma_fence_signal_timestamp_locked); 395 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki