From: bugzilla@dpdk.org
To: dev@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 [thread overview]
Message-ID: <bug-214-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=214
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,
unsigned align, size_t bound)
",
the code:
struct malloc_elem *new_elem = elem_start_pt(elem, size, align, bound);
There should be the code to confirm the new_elem isn't NULL.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-02-25 8:39 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-214-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.