From: Jani Nikula <jani.nikula@intel.com>
To: Patchwork <patchwork@emeril.freedesktop.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BUILD: failure for drm/i915: make struct intel_frontbuffer opaque
Date: Mon, 17 Jun 2024 17:31:14 +0300 [thread overview]
Message-ID: <87le33hc99.fsf@intel.com> (raw)
In-Reply-To: <171863444158.97967.2137691359892388292@a6498e030952>
On Mon, 17 Jun 2024, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm/i915: make struct intel_frontbuffer opaque
> URL : https://patchwork.freedesktop.org/series/134957/
> State : failure
>
> == Summary ==
>
> Error: make failed
> CALL scripts/checksyscalls.sh
> DESCEND objtool
> INSTALL libsubcmd_headers
> CC [M] drivers/gpu/drm/i915/gem/i915_gem_clflush.o
> In file included from ./include/linux/array_size.h:5,
> from ./include/linux/string.h:6,
> from ./include/linux/scatterlist.h:5,
> from ./include/drm/drm_cache.h:36,
> from drivers/gpu/drm/i915/gem/i915_gem_clflush.c:7:
> drivers/gpu/drm/i915/gem/i915_gem_object_frontbuffer.h: In function ‘i915_gem_object_flush_frontbuffer’:
> ./include/linux/rcupdate.h:463:9: error: dereferencing pointer to incomplete type ‘struct intel_frontbuffer’
> 463 | typeof(*p) *local = (typeof(*p) *__force)READ_ONCE(p); \
Ugh, so rcu requires the complete type even if it's about a pointer?
*sigh*
> | ^
> ./include/linux/compiler.h:77:42: note: in definition of macro ‘unlikely’
> 77 | # define unlikely(x) __builtin_expect(!!(x), 0)
> | ^
> ./include/linux/rcupdate.h:582:31: note: in expansion of macro ‘__rcu_access_pointer’
> 582 | #define rcu_access_pointer(p) __rcu_access_pointer((p), __UNIQUE_ID(rcu), __rcu)
> | ^~~~~~~~~~~~~~~~~~~~
> drivers/gpu/drm/i915/gem/i915_gem_object_frontbuffer.h:24:15: note: in expansion of macro ‘rcu_access_pointer’
> 24 | if (unlikely(rcu_access_pointer(obj->frontbuffer)))
> | ^~~~~~~~~~~~~~~~~~
> drivers/gpu/drm/i915/gem/i915_gem_object_frontbuffer.h: In function ‘i915_gem_object_get_frontbuffer’:
> ./include/linux/rcupdate.h:463:9: error: dereferencing pointer to incomplete type ‘struct intel_frontbuffer’
> 463 | typeof(*p) *local = (typeof(*p) *__force)READ_ONCE(p); \
> | ^
> ./include/linux/compiler.h:76:40: note: in definition of macro ‘likely’
> 76 | # define likely(x) __builtin_expect(!!(x), 1)
> | ^
> ./include/linux/rcupdate.h:582:31: note: in expansion of macro ‘__rcu_access_pointer’
> 582 | #define rcu_access_pointer(p) __rcu_access_pointer((p), __UNIQUE_ID(rcu), __rcu)
> | ^~~~~~~~~~~~~~~~~~~~
> drivers/gpu/drm/i915/gem/i915_gem_object_frontbuffer.h:50:14: note: in expansion of macro ‘rcu_access_pointer’
> 50 | if (likely(!rcu_access_pointer(obj->frontbuffer)))
> | ^~~~~~~~~~~~~~~~~~
> make[6]: *** [scripts/Makefile.build:244: drivers/gpu/drm/i915/gem/i915_gem_clflush.o] Error 1
> make[5]: *** [scripts/Makefile.build:485: drivers/gpu/drm/i915] Error 2
> make[4]: *** [scripts/Makefile.build:485: drivers/gpu/drm] Error 2
> make[3]: *** [scripts/Makefile.build:485: drivers/gpu] Error 2
> make[2]: *** [scripts/Makefile.build:485: drivers] Error 2
> make[1]: *** [/home/kbuild/kernel/Makefile:1934: .] Error 2
> make: *** [Makefile:240: __sub-make] Error 2
> Build failed, no error log produced
>
>
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-06-17 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 14:18 [PATCH 0/5] drm/i915: make struct intel_frontbuffer opaque Jani Nikula
2024-06-17 14:18 ` [PATCH 1/5] drm/i915/frontbuffer: un-inline frontbuffer bits checks Jani Nikula
2024-06-17 14:18 ` [PATCH 2/5] drm/i915/frontbuffer: hide ->bits more Jani Nikula
2024-06-17 14:19 ` [PATCH 3/5] drm/i915/frontbuffer: add low-level kref accessors Jani Nikula
2024-06-17 14:19 ` [PATCH 4/5] drm/i915/frontbuffer: hide ->write Jani Nikula
2024-06-17 14:19 ` [PATCH 5/5] drm/i915/frontbuffer: make struct intel_frontbuffer opaque Jani Nikula
2024-06-18 23:54 ` kernel test robot
2024-06-17 14:27 ` ✗ Fi.CI.BUILD: failure for drm/i915: " Patchwork
2024-06-17 14:31 ` Jani Nikula [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=87le33hc99.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.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