All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 393] rte_zmalloc_socket does not zero memory
Date: Fri, 07 Feb 2020 10:18:05 +0000	[thread overview]
Message-ID: <bug-393-3@http.bugs.dpdk.org/> (raw)

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.

                 reply	other threads:[~2020-02-07 10:18 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-393-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.