* [dpdk-dev] [Bug 214] There should be a NULL pointer check about the malloc_elem_alloc
@ 2019-02-25 8:39 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2019-02-25 8:39 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-02-25 8:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-25 8:39 [dpdk-dev] [Bug 214] There should be a NULL pointer check about the malloc_elem_alloc bugzilla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).