[dpdk-dev] [Bug 393] rte_zmalloc_socket does not zero memory

[dpdk-dev] [Bug 393] rte_zmalloc_socket does not zero memory

[bugzilla]

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

            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 cases.
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. 

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 correctly
and does not crash.

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

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.

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