From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1778] MPRQ buffer reference was not decremented upon MLX5_RXQ_CODE_NOMBUF
Date: Thu, 21 Aug 2025 03:06:55 +0000 [thread overview]
Message-ID: <bug-1778-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1778
Bug ID: 1778
Summary: MPRQ buffer reference was not decremented upon
MLX5_RXQ_CODE_NOMBUF
Product: DPDK
Version: 22.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: canary.overflow@gmail.com
Target Milestone: ---
drivers/net/mlx5/mlx5_rx.h mprq_buf_to_pkt(...):
In the external buffer attach case where hdrm_overlap > 0, the code did not
decrement the buffer refcnt if allocation struct rte_mbuf *next =
rte_pktmbuf_alloc(rxq->mp) fails
mprq_buf_to_pkt(...) {
...
if (hdrm_overlap > 0) {
__atomic_add_fetch(&buf->refcnt, 1, __ATOMIC_RELAXED);
...
MLX5_ASSERT(rxq->strd_scatter_en);
struct rte_mbuf *seg = rte_pktmbuf_alloc(rxq->mp);
if (unlikely(seg == NULL))
return MLX5_RXQ_CODE_NOMBUF;
SET_DATA_OFF(seg, 0);
...
}
}
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3100 bytes --]
reply other threads:[~2025-08-21 3:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1778-3@https.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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.