From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id 35AF4A00E6
	for <public@inbox.dpdk.org>; Wed, 15 May 2019 08:18:34 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 42B7D2C17;
	Wed, 15 May 2019 08:18:33 +0200 (CEST)
Received: by dpdk.org (Postfix, from userid 33)
 id 323282C17; Wed, 15 May 2019 08:18:31 +0200 (CEST)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Wed, 15 May 2019 06:18:30 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: ethdev
X-Bugzilla-Version: 18.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wavespider@sina.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: <bug-278-3@http.bugs.dpdk.org/>
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 278] bond_ethdev_rx_burst multithread access bond's
 different queue will crash
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>
Message-ID: <20190515061830.Lw3ZzPBg2Kn5rNvL6GcMCGe5krWvDOKIR2Y01S1OS8Y@z>

https://bugs.dpdk.org/show_bug.cgi?id=3D278

            Bug ID: 278
           Summary: bond_ethdev_rx_burst multithread access bond's
                    different queue will crash
           Product: DPDK
           Version: 18.11
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: wavespider@sina.com
  Target Milestone: ---

when multi-thread access net-bonding interface's different queue, calling
function=20
 below will result in crash because of "out of array boundary":
rte_eth_rx_burst
  -> bond_ethdev_rx_burst

one thread loop over and update internals->active_slave:
if (++internals->active_slave >=3D slave_count)=20
        internals->active_slave =3D 0;
another thread just read internals->active_slave, maybe equal slave_count:

active_slave =3D internals->active_slave;
num_rx_slave =3D
        rte_eth_rx_burst(internals->active_slaves[active_slave], /*Here out=
 of
boundary*/
                 bd_rx_q->queue_id,
                 bufs + num_rx_total, nb_pkts);

default, internals->active_slaves[active_slave] maybe the value is 0, then =
call
rte_eth_rx_burst function:

port-id =3D=3D 0 and queue_id =3D 20 (example):
when port-id =3D=3D 0's interface have not enough queue-number(<20), then w=
ill
result in crash ( dev->data->rx_queues[queue_id] =3D=3D NULL pointer access=
 ).

--=20
You are receiving this mail because:
You are the assignee for the bug.=