From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1559] rte_pktmbuf_pool_create doesn't set the correct rte_errno
Date: Sun, 06 Oct 2024 07:29:28 +0000 [thread overview]
Message-ID: <bug-1559-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1559
Bug ID: 1559
Summary: rte_pktmbuf_pool_create doesn't set the correct
rte_errno
Product: DPDK
Version: 24.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: g199209@gmail.com
Target Milestone: ---
rte_pktmbuf_pool_create --> rte_pktmbuf_pool_create_by_ops -->
rte_mempool_create_empty. In rte_mempool_create_empty, there's such logic: ret
= rte_mempool_set_ops_byname(mp, "xxx", NULL); rte_mempool_set_ops_byname
doesn't set rte_errno, but use return code to indicate errno. So
rte_mempool_create_empty should set rte_errno according to ret, but it forget
to do it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2823 bytes --]
next reply other threads:[~2024-10-06 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 7:29 bugzilla [this message]
2025-03-26 14:08 ` [DPDK/core Bug 1559] rte_pktmbuf_pool_create doesn't set the correct rte_errno bugzilla
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-1559-3@http.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.