From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 19] Crash on initialization if first RTE_MAX_LCORE
 cores are disabled
Date: Sun, 01 Apr 2018 12:24:58 +0000
Message-ID: <bug-19-3@http.dpdk.org/tracker/>
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://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.=