mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: Edwin Peer <epeer@nvidia.com>,
	dakr@kernel.org, aliceryhl@google.com,  phasta@kernel.org,
	sumit.semwal@linaro.org, christian.koenig@amd.com
Cc: jhubbard@nvidia.com, rust-for-linux@vger.kernel.org,
	 dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
	 linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH drm-rust-next] rust: dma_fence: gate abstractions on CONFIG_DMA_SHARED_BUFFER
Date: Thu, 10 Sep 2026 09:17:59 +0200	[thread overview]
Message-ID: <514c6865ede98be45b4a628049ae950b519e0b23.camel@mailbox.org> (raw)
In-Reply-To: <20260909202327.33285-1-epeer@nvidia.com>

On Wed, 2026-09-09 at 13:23 -0700, Edwin Peer wrote:
> The dma_fence abstractions added by commit 3282d5916019 ("rust: Add
> dma_fence abstractions") are compiled unconditionally, but the C
> `dma_fence_*` symbols they reference live in
> drivers/dma-buf/dma-fence.c, which is only built when
> CONFIG_DMA_SHARED_BUFFER=y. Kernels with CONFIG_RUST=y and
> CONFIG_RUST_KERNEL_DOCTESTS=y but CONFIG_DMA_SHARED_BUFFER=n fail
> to link:
> 
>   ld.lld: error: undefined symbol: dma_fence_release
>   >>> referenced by usercopy_64.c
>   >>>               vmlinux.o:(rust_helper_dma_fence_put)
>   ... dma_fence_signal{,_locked}, dma_fence_context_alloc,
>       dma_fence_init, dma_fence_{add,remove}_callback ...
> 
> Wrap the dma_fence.c helper include in the same
> `pub mod dma_buf;` in rust/kernel/lib.rs with a matching #[cfg].

Oh dear, yes. Sorry about that, thx for fixing!

> 
> Fixes: 3282d5916019 ("rust: Add dma_fence abstractions")
> Signed-off-by: Edwin Peer <epeer@nvidia.com>
> Reviewed-by: John Hubbard <jhubbard@nvidia.com>

Reviewed-by: Philipp Stanner <phasta@kernel.org>

> ---
>  rust/helpers/helpers.c | 2 +-
>  rust/kernel/lib.rs     | 1 +
>  2 files changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/rust/helpers/helpers.c b/rust/helpers/helpers.c
> index 609689fba3dd..2c5eecc091c4 100644
> --- a/rust/helpers/helpers.c
> +++ b/rust/helpers/helpers.c
> @@ -57,8 +57,8 @@
>  #include "cred.c"
>  #include "device.c"
>  #include "dma.c"
> -#include "dma_fence.c"
>  #ifdef CONFIG_DMA_SHARED_BUFFER
> +#include "dma_fence.c"
>  #include "dma-resv.c"
>  #endif
>  #include "drm.c"
> diff --git a/rust/kernel/lib.rs b/rust/kernel/lib.rs
> index 72f5527ba66c..f9ef36217bb5 100644
> --- a/rust/kernel/lib.rs
> +++ b/rust/kernel/lib.rs
> @@ -67,6 +67,7 @@
>  pub mod device_id;
>  pub mod devres;
>  pub mod dma;
> +#[cfg(CONFIG_DMA_SHARED_BUFFER)]
>  pub mod dma_buf;
>  pub mod driver;
>  #[cfg(CONFIG_DRM = "y")]

  reply	other threads:[~2026-09-10  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 20:23 Edwin Peer
2026-09-10  7:17 ` Philipp Stanner [this message]
2026-09-10 13:36 ` Danilo Krummrich

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=514c6865ede98be45b4a628049ae950b519e0b23.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=aliceryhl@google.com \
    --cc=christian.koenig@amd.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=epeer@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=phasta@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sumit.semwal@linaro.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

all inboxes | Powered by JetHome®