All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Philipp Stanner <phasta@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v5 6/6] rust: drm: Add JobQueue
Date: Thu, 15 Oct 2026 15:20:30 +0800	[thread overview]
Message-ID: <202610151526.B43xvcc0-lkp@intel.com> (raw)
In-Reply-To: <20261009191124.1022902-8-phasta@kernel.org>

Hi Philipp,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on next-20261008]
[cannot apply to rust/rust-next drm/drm-next v7.3-rc6 v7.3-rc5 v7.3-rc4 linus/master v7.3-rc7]
[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/Philipp-Stanner/rust-DmaFence-remove-static-lifetime/20261009-211119
base:   next-20261008
patch link:    https://lore.kernel.org/r/20261009191124.1022902-8-phasta%40kernel.org
patch subject: [RFC PATCH v5 6/6] rust: drm: Add JobQueue
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20261015/202610151526.B43xvcc0-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261015/202610151526.B43xvcc0-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/202610151526.B43xvcc0-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0432]: unresolved imports `kernel::workqueue::new_scoped_work`, `kernel::workqueue::ScopedWork`, `kernel::workqueue::ScopedWorkItem`, `kernel::workqueue::ScopedWorkRef`
   --> rust/kernel/drm/job_queue.rs:60:9
   |
   60 |         new_scoped_work,
   |         ^^^^^^^^^^^^^^^ no `new_scoped_work` in `workqueue`
   61 | //        ScopedQueue,
   62 |         ScopedWork,
   |         ^^^^^^^^^^ no `ScopedWork` in `workqueue`
   63 |         ScopedWorkItem,
   |         ^^^^^^^^^^^^^^ no `ScopedWorkItem` in `workqueue`
   64 |         ScopedWorkRef,
   |         ^^^^^^^^^^^^^ no `ScopedWorkRef` in `workqueue`
   |
   help: a similar name exists in the module
   |
   60 -         new_scoped_work,
   60 +         new_delayed_work,
   |
--
>> error[E0425]: cannot find function `system_dfl` in module `workqueue`
   --> rust/kernel/drm/job_queue.rs:257:29
   |
   257 |         unsafe { workqueue::system_dfl().enqueue_scoped(&*self.submit_worker) };
   |                             ^^^^^^^^^^
   |
   ::: rust/kernel/workqueue.rs:1102:1
   |
   1102 | pub fn system_bh() -> &'static Queue {
   | ------------------------------------ similarly named function `system_bh` defined here
   |
   help: a function with a similar name exists
   |
   257 -         unsafe { workqueue::system_dfl().enqueue_scoped(&*self.submit_worker) };
   257 +         unsafe { workqueue::system_bh().enqueue_scoped(&*self.submit_worker) };
   |
--
>> error[E0277]: `impl PinInit<Revocable<Lock<impl PinInit<..., ...>, ...>>>` cannot be used to initialize `Revocable<lock::Lock<JobQueueInner<'_, T>, SpinLockIrqBackend>>` with error `_`
   --> rust/kernel/drm/job_queue.rs:416:22
   |
   416 |               inner <- Revocable::new(new_spinlock_irq!(try_pin_init!(JobQueueInner {
   |  ___________________--_^
   | |                   |
   | |                   required by a bound introduced by this call
   417 | |                 submit_worker_active: false,
   418 | |                 // SAFETY: `this` is valid. The lifetimes ensure that the reference remains valid.
   419 | |                 submit_worker <- new_scoped_work!("JobQueueSubmitWorker", Ok(SubmitWorker { jq: unsafe { &*this.as_ptr() } })),
   ...    |
   422 | |                 capacity,
   423 | |             }))),
   | |________________^ unsatisfied trait bound
   |
   = help: the trait `pin_init::PinInit<Revocable<lock::Lock<JobQueueInner<'_, T>, SpinLockIrqBackend>>, _>` is not implemented for `impl PinInit<Revocable<Lock<impl PinInit<..., ...>, ...>>>`
   help: the following other types implement trait `pin_init::PinInit<T, E>`
   --> rust/pin-init/src/lib.rs:1063:1
   |
   1063 | / unsafe impl<T: ?Sized, E, I, F> PinInit<T, E> for ChainPinInit<I, F, T, E>
   1064 | | where
   1065 | |     I: PinInit<T, E>,
   1066 | |     F: FnOnce(Pin<&mut T>) -> Result<(), E>,
   | |____________________________________________^ `ChainPinInit<I, F, T, E>`
   ...
   1162 | / unsafe impl<T: ?Sized, E, I, F> PinInit<T, E> for ChainInit<I, F, T, E>
   1163 | | where
   1164 | |     I: Init<T, E>,
   1165 | |     F: FnOnce(&mut T) -> Result<(), E>,
   | |_______________________________________^ `ChainInit<I, F, T, E>`
   ...
   1502 |   unsafe impl<T, E> PinInit<T, E> for Result<T, E> {
   |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `core::result::Result<T, E>`
   note: required by a bound in `pin_init::__internal::Slot::<pin_init::__internal::Pinned, T>::init`
   --> rust/pin-init/src/__internal.rs:266:37
   |
   266 |     pub fn init<E>(self, init: impl PinInit<T, E>) -> Result<DropGuard<Pinned, T>, E> {
   |                                     ^^^^^^^^^^^^^ required by this bound in `Slot::<Pinned, T>::init`
   = note: the full name for the type has been written to 'kernel.long-type-12147038180072536476.txt'
   = note: consider using `--verbose` to print the full type name to the console

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

  parent reply	other threads:[~2026-10-15  7:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 19:11 [RFC PATCH v5 0/6] rust: Add drm::JobQueue Philipp Stanner
2026-10-09 19:11 ` [RFC PATCH v5 1/6] rust: DmaFence: remove static lifetime Philipp Stanner
2026-10-09 19:24   ` sashiko-bot
2026-10-09 19:11 ` [RFC PATCH v5 2/6] rust: DmaFence: Implement Deref for FenceContext Philipp Stanner
2026-10-09 19:19   ` sashiko-bot
2026-10-09 19:11 ` [RFC PATCH v5 3/6] rust: DmaFence: Don't drop on signal Philipp Stanner
2026-10-09 19:26   ` sashiko-bot
2026-10-09 19:11 ` [RFC PATCH v5 4/6] rust: DmaFence: [RFC] Add Signaler Philipp Stanner
2026-10-09 19:23   ` sashiko-bot
2026-10-09 19:11 ` [RFC PATCH v5 5/6] rust: DmaFence: Replace call_rcu() with synchronize_rcu() Philipp Stanner
2026-10-09 19:25   ` sashiko-bot
2026-10-09 19:11 ` [RFC PATCH v5 6/6] rust: drm: Add JobQueue Philipp Stanner
2026-10-09 19:24   ` sashiko-bot
2026-10-15  7:20   ` kernel test robot [this message]
2026-10-11  0:22 ` [RFC PATCH v5 0/6] rust: Add drm::JobQueue Daniel Almeida
2026-10-12  8:17   ` Philipp Stanner

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=202610151526.B43xvcc0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=phasta@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.