public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Christian König " <christian.koenig@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Boris Brezillon <bbrezillon@kernel.org>
Subject: [linux-next:master 728/13151] drivers/gpu/drm/i915/selftests/i915_active.c:326:23: error: no member named 'lock' in 'struct dma_fence'
Date: Sat, 11 Apr 2026 01:08:30 +0800	[thread overview]
Message-ID: <202604110107.XKR8jZTJ-lkp@intel.com> (raw)

Hi Christian,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   3fa7d958829eb9bc3b469ed07f11de3d2804ef71
commit: 1f32f310a13c9fb67a9993ab67f596b3f960206f [728/13151] dma-buf: inline spinlock for fence protection v5
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20260411/202604110107.XKR8jZTJ-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260411/202604110107.XKR8jZTJ-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/202604110107.XKR8jZTJ-lkp@intel.com/

Note: the linux-next/master HEAD 3fa7d958829eb9bc3b469ed07f11de3d2804ef71 builds fine.
      It may have been fixed somewhere.

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/i915/i915_active.c:1177:
>> drivers/gpu/drm/i915/selftests/i915_active.c:326:23: error: no member named 'lock' in 'struct dma_fence'
     326 |         spin_lock_irq(fence->lock);
         |                       ~~~~~  ^
   drivers/gpu/drm/i915/selftests/i915_active.c:328:25: error: no member named 'lock' in 'struct dma_fence'
     328 |         spin_unlock_irq(fence->lock); /* serialise with fence->cb_list */
         |                         ~~~~~  ^
   2 errors generated.


vim +326 drivers/gpu/drm/i915/selftests/i915_active.c

38813767c7c5d9 Chris Wilson 2019-11-01  316  
e3e7aeec3281af Chris Wilson 2020-03-06  317  static void active_flush(struct i915_active *ref,
e3e7aeec3281af Chris Wilson 2020-03-06  318  			 struct i915_active_fence *active)
e3e7aeec3281af Chris Wilson 2020-03-06  319  {
e3e7aeec3281af Chris Wilson 2020-03-06  320  	struct dma_fence *fence;
e3e7aeec3281af Chris Wilson 2020-03-06  321  
e3e7aeec3281af Chris Wilson 2020-03-06  322  	fence = xchg(__active_fence_slot(active), NULL);
e3e7aeec3281af Chris Wilson 2020-03-06  323  	if (!fence)
e3e7aeec3281af Chris Wilson 2020-03-06  324  		return;
e3e7aeec3281af Chris Wilson 2020-03-06  325  
e3e7aeec3281af Chris Wilson 2020-03-06 @326  	spin_lock_irq(fence->lock);
e3e7aeec3281af Chris Wilson 2020-03-06  327  	__list_del_entry(&active->cb.node);
e3e7aeec3281af Chris Wilson 2020-03-06  328  	spin_unlock_irq(fence->lock); /* serialise with fence->cb_list */
e3e7aeec3281af Chris Wilson 2020-03-06  329  	atomic_dec(&ref->count);
e3e7aeec3281af Chris Wilson 2020-03-06  330  
e3e7aeec3281af Chris Wilson 2020-03-06  331  	GEM_BUG_ON(!test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->flags));
e3e7aeec3281af Chris Wilson 2020-03-06  332  }
e3e7aeec3281af Chris Wilson 2020-03-06  333  

:::::: The code at line 326 was first introduced by commit
:::::: e3e7aeec3281af446d7410d6982020e1aa5795fc drm/i915/selftests: Apply a heavy handed flush to i915_active

:::::: TO: Chris Wilson <chris@chris-wilson.co.uk>
:::::: CC: Chris Wilson <chris@chris-wilson.co.uk>

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

                 reply	other threads:[~2026-04-10 17:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202604110107.XKR8jZTJ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bbrezillon@kernel.org \
    --cc=christian.koenig@amd.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox