From: sashiko-bot@kernel.org
To: "Andrei-Alexandru Bleortu" <me@andrei-z.com>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH RFC 1/3] IB/iser: Post header-only PDUs inline
Date: Thu, 15 Oct 2026 13:01:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-172888@kernel.org> (raw)
In-Reply-To: <20261015125118.2966247-2-me@andrei-z.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] iser: DMA mapping leak on iser_send_data_out() error path
--
commit 9c1d70cc4e6b5a103b601d5536559ca76fc30e86
Author: Andrei-Alexandru Bleortu <me@andrei-z.com>
IB/iser: Post header-only PDUs inline
iser_post_send() posts every PDU by reference, and the QP asks for no
inline data. Before the HCA can send a SCSI command it therefore has
to DMA-read the 76 bytes of iSER and iSCSI headers from host memory,
and that read is on the latency path of every command.
> diff --git a/drivers/infiniband/ulp/iser/iser_verbs.c b/drivers/infiniband/ulp/iser/iser_verbs.c
> index ab2a27d23478a..6319d7fd17cf1 100644
> --- a/drivers/infiniband/ulp/iser/iser_verbs.c
> +++ b/drivers/infiniband/ulp/iser/iser_verbs.c
[ ... ]
> @@ -870,6 +882,19 @@ int iser_post_send(struct ib_conn *ib_conn, struct iser_tx_desc *tx_desc)
> wr->opcode = IB_WR_SEND;
> wr->send_flags = IB_SEND_SIGNALED;
>
> + /*
> + * Post a header-only PDU inline if it fits in the granted inline
> + * size, so the HCA does not have to DMA-read it from host memory.
> + * The CPU copies inline data from a kernel virtual address, so point
> + * the SGE at the headers.
> + */
> + tx_desc->tx_sg[0].addr = tx_desc->dma_addr;
> + if (tx_desc->num_sge == 1 &&
> + tx_desc->tx_sg[0].length <= ib_conn->max_inline_data) {
> + tx_desc->tx_sg[0].addr = (uintptr_t)&tx_desc->iser_header;
> + wr->send_flags |= IB_SEND_INLINE;
> + }
> +
> if (tx_desc->inv_wr.next)
> first_wr = &tx_desc->inv_wr;
> else if (tx_desc->reg_wr.wr.next)
[Severity: Medium]
If iser_post_send() returns an error here (such as when ib_post_send() fails),
iser_send_data_out() handles the error by jumping to send_data_out_error:
drivers/infiniband/ulp/iser/iser_initiator.c:iser_send_data_out() {
...
err = iser_post_send(&iser_conn->ib_conn, tx_desc);
if (!err)
return 0;
send_data_out_error:
kmem_cache_free(ig.desc_cache, tx_desc);
iser_err("conn %p failed err %d\n", conn, err);
return err;
}
When tx_desc was initialized earlier in iser_initialize_task_headers(), a DMA
mapping was created.
Does freeing tx_desc without calling ib_dma_unmap_single() cause a permanent
leak of the IOMMU DMA mapping?
This could potentially exhaust IOMMU space or cause memory corruption if the
address is reused.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261015125118.2966247-1-me@andrei-z.com?part=1
next prev parent reply other threads:[~2026-10-15 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:51 [PATCH RFC 0/3] RDMA: Post small ULP command messages inline Andrei-Alexandru Bleortu
2026-10-15 12:51 ` [PATCH RFC 1/3] IB/iser: Post header-only PDUs inline Andrei-Alexandru Bleortu
2026-10-15 13:01 ` sashiko-bot [this message]
2026-10-15 13:32 ` Andrei-Alexandru Bleortu
2026-10-15 14:08 ` Andrei-Alexandru Bleortu
2026-10-15 12:51 ` [PATCH RFC 2/3] RDMA/srp: Post command IUs inline Andrei-Alexandru Bleortu
2026-10-15 13:02 ` sashiko-bot
2026-10-15 17:24 ` Bart Van Assche
2026-10-15 18:22 ` Andrei-Alexandru Bleortu
2026-10-15 12:51 ` [PATCH RFC 3/3] RDMA/rtrs: Post client read requests inline Andrei-Alexandru Bleortu
2026-10-15 13:07 ` sashiko-bot
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=sashiko-outbox-172888@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=me@andrei-z.com \
--cc=sashiko-reviews@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 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.