From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id 6ABC15F34; Sun, 1 Apr 2018 14:24:58 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Sun, 01 Apr 2018 12:24:58 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: solal.pirelli@gmail.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- 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://dpdk.org/tracker/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 19] Crash on initialization if first RTE_MAX_LCORE cores are disabled 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: Sun, 01 Apr 2018 12:24:58 -0000 https://dpdk.org/tracker/show_bug.cgi?id=3D19 Bug ID: 19 Summary: Crash on initialization if first RTE_MAX_LCORE cores are disabled Product: DPDK Version: unspecified Hardware: All OS: All Status: CONFIRMED Severity: minor Priority: Normal Component: core Assignee: dev@dpdk.org Reporter: solal.pirelli@gmail.com Target Milestone: --- In eal_common_options.c, the master lcore is found by looking for the first enabled lcore (http://dpdk.org/browse/dpdk/tree/lib/librte_eal/common/eal_common_options.= c?h=3Dv18.02#n1213). However, there is no check for the case where no enabled lcore is found. In= the (unlikely!) case of all first RTE_MAX_LCORE cores being disabled, the next instruction will cause an out-of-bounds array access, probably crashing the app. --=20 You are receiving this mail because: You are the assignee for the bug.=