From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 214] There should be a NULL pointer check about the
 malloc_elem_alloc
Date: Mon, 25 Feb 2019 08:39:56 +0000
Message-ID: <bug-214-3@http.bugs.dpdk.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
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=3D214

            Bug ID: 214
           Summary: There should be a NULL pointer check about the
                    malloc_elem_alloc
           Product: DPDK
           Version: 17.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: andy01011501@163.com
  Target Milestone: 17.11

In file "/lib/librte_eal/common/malloc_elem.c",
the function:
"
    struct malloc_elem * malloc_elem_alloc(struct malloc_elem *elem, size_t
size,=20
    unsigned align, size_t bound)
",
the code:
struct malloc_elem *new_elem =3D elem_start_pt(elem, size, align, bound);

There should be the code to confirm the new_elem isn't NULL.

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