From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1378] Coverity defect reported in rte_mempool.h : Out-of-bounds access
Date: Thu, 08 Feb 2024 19:14:53 +0000 [thread overview]
Message-ID: <bug-1378-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1378
Bug ID: 1378
Summary: Coverity defect reported in rte_mempool.h :
Out-of-bounds access
Product: DPDK
Version: 22.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: dmckie@avaya.com
Target Milestone: ---
I have searched unsuccessfully for information on this potential issue reported
by coverity.
Is this a known issue? or a false-positive coverity finding?
Category: Memory - corruptions
file: dpdk/include/rte_mempool.h
static __rte_always_inline void rte_mempool_put(struct rte_mempool *mp, void
*obj)
{
Out-of-bounds access (OVERRUN)
overrun-buffer-val: Overrunning buffer pointed to by &obj of 8 bytes by passing
it to a function which accesses it at byte offset 463.
rte_mempool_put_bulk(mp, &obj, 1);
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2988 bytes --]
reply other threads:[~2024-02-08 19:14 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-1378-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.