Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: kernel test robot <lkp@intel.com>
Cc: Lyude Paul <lyude@redhat.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [linux-next:master 2964/10599] error[E0609]: no field `dev` on type `drm_gem_object`
Date: Fri, 21 Nov 2025 09:06:17 +0000	[thread overview]
Message-ID: <aSAriWs68Hlng-nS@google.com> (raw)
In-Reply-To: <202511210649.lhQnt194-lkp@intel.com>

On Fri, Nov 21, 2025 at 06:47:35AM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   88cbd8ac379cf5ce68b7efcfd4d1484a6871ee0b
> commit: d3917368ebc5cd89d7d08eab4673e5c4c73ff42f [2964/10599] rust: drm/gem: Remove Object.dev
> config: um-randconfig-001-20251121 (https://download.01.org/0day-ci/archive/20251121/202511210649.lhQnt194-lkp@intel.com/config)
> compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9e9fe08b16ea2c4d9867fb4974edf2a3776d6ece)
> rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251121/202511210649.lhQnt194-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/202511210649.lhQnt194-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
> >> error[E0609]: no field `dev` on type `drm_gem_object`
>    --> rust/kernel/drm/gem/mod.rs:231:57
>    |
>    231 |         unsafe { drm::Device::from_raw((*self.as_raw()).dev) }
>    |                                                         ^^^ unknown field
>    |
>    = note: available field is: `_address`

I tried reproducing this on commit d3917368ebc5, but I got this error
instead:

	error[E0432]: unresolved imports `core::sync::atomic::AtomicI64`, `core::sync::atomic::AtomicU64`
	  --> <linux>/rust/kernel/debugfs/traits.rs:12:27
	   |
	12 |     AtomicI16, AtomicI32, AtomicI64, AtomicI8, AtomicIsize, AtomicU16, AtomicU32, AtomicU64,
	   |                           ^^^^^^^^^ no `AtomicI64` in `sync::atomic`              ^^^^^^^^^ no `AtomicU64` in `sync::atomic`
	   |
	help: a similar name exists in the module
	   |
	12 |     AtomicI16, AtomicI32, AtomicI32, AtomicI8, AtomicIsize, AtomicU16, AtomicU32, AtomicU64,
	   |                           ~~~~~~~~~
	help: a similar name exists in the module
	   |
	12 |     AtomicI16, AtomicI32, AtomicI64, AtomicI8, AtomicIsize, AtomicU16, AtomicU32, AtomicU32,
	   |                                                                                   ~~~~~~~~~
	
	error[E0560]: struct `bindings::drm_gem_object_funcs` has no field named `vmap`
	   --> <linux>/rust/kernel/drm/gem/mod.rs:188:9
	    |
	188 |         vmap: None,
	    |         ^^^^ `bindings::drm_gem_object_funcs` does not have this field
	    |
	    = note: available fields are: `kernel_vmap`
	
	error: aborting due to 2 previous errors

This was with ARCH=um SUBARCH=i386 in my make invocation and the
provided config.

Perhaps this config is just not working in general?

Alice

  parent reply	other threads:[~2025-11-21  9:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 22:47 [linux-next:master 2964/10599] error[E0609]: no field `dev` on type `drm_gem_object` kernel test robot
2025-11-21  7:45 ` Alice Ryhl
2025-11-21  9:06 ` Alice Ryhl [this message]
2025-11-21 12:53   ` Philip Li
2025-11-21 15:26   ` Miguel Ojeda
2025-11-22  7:37     ` David Gow

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=aSAriWs68Hlng-nS@google.com \
    --to=aliceryhl@google.com \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=lyude@redhat.com \
    --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