Re: [moderation/CI] Re: NTB: Add direct TX/RX using PCI endpoint DMA

On Mon, Aug 10, 2026 at 02:44:57PM -0700, syzbot ci wrote:
> syzbot ci has tested the following series
> 
> [v1] NTB: Add direct TX/RX using PCI endpoint DMA
> https://lore.kernel.org/all/[email protected]
> * [PATCH 01/16] NTB: ntb_transport: Abort link setup on QP MW allocation failure
> * [PATCH 02/16] NTB: ntb_transport: Reject oversized TX buffers
> * [PATCH 03/16] NTB: ntb_transport: Start TX offload thread after queue setup
> * [PATCH 04/16] NTB: ntb_transport: Stop QP work before freeing a queue
> * [PATCH 05/16] NTB: ntb_transport: Run RX processing on system workqueue
> * [PATCH 06/16] NTB: ntb_transport: Define direct-DMA shared state
> * [PATCH 07/16] NTB: ntb_transport: Negotiate direct-DMA queue layout
> * [PATCH 08/16] NTB: ntb_transport: Add opt-in direct-DMA channel reservation
> * [PATCH 09/16] NTB: ntb_transport: Allocate direct-DMA queue state
> * [PATCH 10/16] NTB: ntb_transport: Implement direct-DMA QP session handshake
> * [PATCH 11/16] NTB: ntb_transport: Implement direct-DMA RX buffer publication
> * [PATCH 12/16] NTB: ntb_transport: Implement direct-DMA TX submission
> * [PATCH 13/16] NTB: ntb_transport: Implement safe direct-DMA teardown
> * [PATCH 14/16] NTB: ntb_transport: Enable direct-DMA queues
> * [PATCH 15/16] NTB: ntb_transport: Report the direct-DMA payload limit
> * [PATCH 16/16] NTB: ntb_transport: Add optional polling for direct-DMA RX
> 
> and found the following issue:
> kernel build error
> 
> Full report is available here:
> https://ci.syzbot.org/series/47a24886-7793-47c5-afcb-099b60961996
> 
> ***
> 
> kernel build error
> 
> tree:      net-next

This series implementation uses a new API introduced by Frank's series:
https://lore.kernel.org/r/[email protected]/
which is queued for v7.3 and is not yet present in net-next.

If accepted, I expected this series go through ntb-next (rather than net-next),
most likely for v7.4, by which time the API should be in the tree.

#syz invalid

Best regards,
Koichiro


> URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
> base:      001b5d347d8ba39b2dccaefcc57967b18caec8fe
> arch:      amd64
> compiler:  Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> config:    https://ci.syzbot.org/builds/ed6a2ec8-60c9-4ac5-8010-3ffdf21a07e7/config
> 
> drivers/ntb/ntb_transport.c:3052:13: error: call to undeclared function 'dmaengine_prep_config_single_safe'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> drivers/ntb/ntb_transport.c:3052:11: error: incompatible integer to pointer conversion assigning to 'struct dma_async_tx_descriptor *' from 'int' [-Wint-conversion]
> drivers/ntb/ntb_transport.c:3072:14: error: incompatible integer to pointer conversion assigning to 'struct dma_async_tx_descriptor *' from 'int' [-Wint-conversion]
> drivers/ntb/ntb_transport.c:3149:16: error: call to undeclared function 'dmaengine_prep_config_single_safe'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> drivers/ntb/ntb_transport.c:3149:14: error: incompatible integer to pointer conversion assigning to 'struct dma_async_tx_descriptor *' from 'int' [-Wint-conversion]
> 
> ***
> 
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
>   Tested-by: [email protected]
> 
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at [email protected].
> 
> To test a patch for this bug, please reply with `#syz test`
> (should be on a separate line).
> 
> The patch should be attached to the email.
> Note: arguments like custom git repos and branches are not supported.
> 
> The email will later be sent to:
> [[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]]
> 
> If the report looks fine to you, reply with:
> #syz upstream
> 
> If the report is a false positive, reply with
> #syz invalid
>