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 4DCB4A00E6
	for <public@inbox.dpdk.org>; Thu, 18 Apr 2019 11:38:58 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 1FCC41B91A;
	Thu, 18 Apr 2019 11:38:57 +0200 (CEST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id 5ACD21B8C8
 for <dev@dpdk.org>; Thu, 18 Apr 2019 11:38:55 +0200 (CEST)
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com
 [10.5.11.15])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id AFF84305390F;
 Thu, 18 Apr 2019 09:38:54 +0000 (UTC)
Received: from [10.36.117.214] (ovpn-117-214.ams2.redhat.com [10.36.117.214])
 by smtp.corp.redhat.com (Postfix) with ESMTP id 9FC6E5D6A9;
 Thu, 18 Apr 2019 09:38:51 +0000 (UTC)
To: =?UTF-8?Q?Przemys=c5=82aw_O=c5=82tarzewski?= <p.oltarzewski@gmail.com>,
 David Marchand <david.marchand@redhat.com>
Cc: Chas Williams <3chas3@gmail.com>, dev <dev@dpdk.org>
References: <bug-248-3@http.bugs.dpdk.org/>
 <CAJFAV8y5V9v1dA7Vx3_7ZoqupYvhvD-BtbR1dt5KOsCt5J2S+g@mail.gmail.com>
 <CAFJX8XjAp8pMf5gwFrSz_Aw_M9Lw9QmTC3h0Wp7hTOzkZWzwEg@mail.gmail.com>
 <CAJFAV8z5q=fSPXj7t9yA=VbcVhHmV08G4q7_27pAQb3q2B9TYw@mail.gmail.com>
 <CAFJX8XjvATKzCfscJHjVVvxgTyEa_h7CovjDu5fTUq3rXH0Jsw@mail.gmail.com>
From: Kevin Traynor <ktraynor@redhat.com>
Message-ID: <0eb9ec0c-5890-3d05-280c-abc39b8f37c8@redhat.com>
Date: Thu, 18 Apr 2019 10:38:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAFJX8XjvATKzCfscJHjVVvxgTyEa_h7CovjDu5fTUq3rXH0Jsw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.5.110.41]); Thu, 18 Apr 2019 09:38:54 +0000 (UTC)
Subject: Re: [dpdk-dev] [Bug 248] Bonding PMD: Invalid array dimension in TX
 burst for 802.3ad mode with fast queue leads to SEGFAULT
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: <20190418093850.Hb_HcNEVCTryjlO5sGhdjUmjIPvqyp7U2k1wt1ty7lI@z>

On 15/04/2019 10:50, Przemysław Ołtarzewski wrote:
> Hello,
> 
> Last week I attempted to migrate our system from DPDK 18.11.1 to current
> master with David's patches applied. I haven't been able to make it work
> correctly - probably due to other changes in master since 18.11.1 - so
> unfortunately I cannot confirm that David's patchset solves the issue
> (although from source code analysis it seems that array dimension has been
> fixed).
> 
> I have already spent considerable time migrating from 17.11.5 to 18.11.1
> and for the time being I need to focus on diagnosing the original issue in
> our system that led to discovery of invalid array dimension. I will try
> again when I have some more time.
> 

Hi, assuming that David's patches are merged to master DPDK, then they
should be part of 18.11.2. There are also several other bonding fixes
that will be part of 18.11.2. So you could consider taking the 18.11
stable branch and applying the patches you need on top of that to test.

Kevin.

> Best Regards,
> Przemysław Ołtarzewski