diff options
| author | Edwin Peer <epeer@nvidia.com> | 2026-09-09 13:23:27 -0700 |
|---|---|---|
| committer | Danilo Krummrich <dakr@kernel.org> | 2026-09-10 15:28:41 +0200 |
| commit | 73e5616f3d197c1af5a04a481fe0f13aa3913bd1 (patch) | |
| tree | 9de714f5d9bb780731cd956d73df6c5cc8a7bc2e /tools/lib/python/kdoc/python_version.py | |
| parent | 10186439b81f4d0a3c7581a3a012847fba6d140e (diff) | |
rust: dma_fence: gate abstractions on CONFIG_DMA_SHARED_BUFFER
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].
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>
Link: https://patch.msgid.link/20260909202327.33285-1-epeer@nvidia.com
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
