From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 4F9CBA0541;
	Fri,  7 Feb 2020 11:18:08 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 2BE661C024;
	Fri,  7 Feb 2020 11:18:07 +0100 (CET)
Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178])
 by dpdk.org (Postfix) with ESMTP id BDD8C1C011
 for <dev@dpdk.org>; Fri,  7 Feb 2020 11:18:05 +0100 (CET)
Received: by inbox.dpdk.org (Postfix, from userid 33)
 id 9E2F3A0542; Fri,  7 Feb 2020 11:18:05 +0100 (CET)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Fri, 07 Feb 2020 10:18:05 +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: 19.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: pavel.krauz@anritsu.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: <bug-393-3@http.bugs.dpdk.org/>
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
MIME-Version: 1.0
Subject: [dpdk-dev] [Bug 393] rte_zmalloc_socket does not zero memory
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

https://bugs.dpdk.org/show_bug.cgi?id=3D393

            Bug ID: 393
           Summary: rte_zmalloc_socket does not zero memory
           Product: DPDK
           Version: 19.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: pavel.krauz@anritsu.com
  Target Milestone: ---

Hello,
It seems that rte_zmalloc_socket does not return zeroed memory on some case=
s.
It seems to work OK on all but HP G10 server where I was testing application
that tried to create rte fragment table and do IP defragementation where it
crashed on some of the structure members.=20

I put check into rte_zmalloc_socket to see if the memory was really zeroed =
and
it was not! Also if I zero the memory then the defragmentation works correc=
tly
and does not crash.

I see from google that there were problems like this in the past with non
zeroed rte_zmalloc_socket.=20

I have tested also the 19.02 version and it has same problem.

this is on Centos 7.3 with linux kernel 3.10.0-514.el7.x86_64. Don't know if
the linux itself can return non-zeroed memory in some case to dpdk lib.

--=20
You are receiving this mail because:
You are the assignee for the bug.=