From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id F3FC63256; Mon, 25 Feb 2019 09:39:55 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Mon, 25 Feb 2019 08:39:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 17.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: andy01011501@163.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: 17.11 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 214] There should be a NULL pointer check about the malloc_elem_alloc X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2019 08:39:56 -0000 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.=