From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id F188943AB5; Thu, 8 Feb 2024 20:14:55 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7FCA342DF9; Thu, 8 Feb 2024 20:14:55 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 1BB6340295 for ; Thu, 8 Feb 2024 20:14:54 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id ED47B43AB9; Thu, 8 Feb 2024 20:14:53 +0100 (CET) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 22.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dmckie@avaya.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17074196930.8B6dEed.1413161 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17074196930.8B6dEed.1413161 Date: Thu, 8 Feb 2024 20:14:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1378 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 repo= rted by coverity.=20 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 pas= sing it to a function which accesses it at byte offset 463. rte_mempool_put_bulk(mp, &obj, 1); --=20 You are receiving this mail because: You are the assignee for the bug.= --17074196930.8B6dEed.1413161 Date: Thu, 8 Feb 2024 20:14:53 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1378
Summary Coverity defect reported in rte_mempool.h : Out-of-bounds acc= ess
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.=20

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.
=20=20=20=20=20=20=20=20=20=20
= --17074196930.8B6dEed.1413161--