From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua1-f48.google.com (mail-ua1-f48.google.com [209.85.222.48]) by dpdk.org (Postfix) with ESMTP id 9110E1B0FC for ; Wed, 10 Apr 2019 14:56:37 +0200 (CEST) Received: by mail-ua1-f48.google.com with SMTP id g8so741297uaj.0 for ; Wed, 10 Apr 2019 05:56:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4OUPPL2R4fAxiFeyHGLf/hF4c1uA48t9AT5LhBXsgZg=; b=AiY2AgpdhXwiDCAuUfjSFrEzf4NZevwPNWb2ABmfhGTTbHXben602fYXSpElnI9fgE 2uPCwuwdbo7VyjQZnjlUQhdpG7iFXqeV5H4MHBW2zFKToauOa5Mpkda6PcVf06xioQUX 1gomlwLpgggb4dOOjAxnN/NUTZSnMHKCx3G8w2pmktygenBAwkcWVQdZq0GJAe4uRVzH /CZTu9T9i4B4YwP8SqFM6Ggmr5kg0r3YQ6j4q6chYtigK7ByB5WTps1Fm/Aw+IDs2QI9 tZ67uuA5gFyr0zKuc36/OmeMMBZIAiBo+8HEKzkbbR/5t3ItDXZjwj8Y2pqtdZZEI2oC 48gA== X-Gm-Message-State: APjAAAUrgpd8azOz/xOudCtMqLNBJddFnVGfg8ZCaz+o9OdWBuWoHI1m 07ZKNIxMsqqPco8q0+IYIit3A/grS3NkAMrKEdBX6Q== X-Google-Smtp-Source: APXvYqxvbX5HnbdxCxn0UkGL+A+x3MpHc4vy95/TcXNzuKlfBpKjmHOwVBhcsgnzOWyJjNgxBrlFywGyzVrnPfmB3R4= X-Received: by 2002:ab0:73d3:: with SMTP id m19mr22677431uaq.46.1554900996981; Wed, 10 Apr 2019 05:56:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 10 Apr 2019 14:56:25 +0200 Message-ID: To: =?UTF-8?B?UHJ6ZW15c8WCYXcgT8WCdGFyemV3c2tp?= Cc: Chas Williams <3chas3@gmail.com>, dev Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2019 12:56:37 -0000 On Wed, Apr 10, 2019 at 1:33 PM Przemys=C5=82aw O=C5=82tarzewski < p.oltarzewski@gmail.com> wrote: > Hello David, > > I can merge these fixes and run our system using patched DPDK version. > Then report back any problems / improvements I observe. I can also walk > through source code changes and check for anything questionable. > > Unfortunately I lack deep enough understanding of DPDK source code to tes= t > these fixes comprehensively and I have been short on time recently as wel= l, > so that's the best I can do right now. > Please, be aware that other fixes have been already merged in master since 18.11. https://git.dpdk.org/dpdk/log/drivers/net/bonding I just sent the patchset that should fix your issue: http://patchwork.dpdk.org/project/dpdk/list/?series=3D4240 --=20 David Marchand From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 0D3F2A0096 for ; Wed, 10 Apr 2019 14:56:39 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B07581B120; Wed, 10 Apr 2019 14:56:38 +0200 (CEST) Received: from mail-ua1-f48.google.com (mail-ua1-f48.google.com [209.85.222.48]) by dpdk.org (Postfix) with ESMTP id 9110E1B0FC for ; Wed, 10 Apr 2019 14:56:37 +0200 (CEST) Received: by mail-ua1-f48.google.com with SMTP id g8so741297uaj.0 for ; Wed, 10 Apr 2019 05:56:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4OUPPL2R4fAxiFeyHGLf/hF4c1uA48t9AT5LhBXsgZg=; b=AiY2AgpdhXwiDCAuUfjSFrEzf4NZevwPNWb2ABmfhGTTbHXben602fYXSpElnI9fgE 2uPCwuwdbo7VyjQZnjlUQhdpG7iFXqeV5H4MHBW2zFKToauOa5Mpkda6PcVf06xioQUX 1gomlwLpgggb4dOOjAxnN/NUTZSnMHKCx3G8w2pmktygenBAwkcWVQdZq0GJAe4uRVzH /CZTu9T9i4B4YwP8SqFM6Ggmr5kg0r3YQ6j4q6chYtigK7ByB5WTps1Fm/Aw+IDs2QI9 tZ67uuA5gFyr0zKuc36/OmeMMBZIAiBo+8HEKzkbbR/5t3ItDXZjwj8Y2pqtdZZEI2oC 48gA== X-Gm-Message-State: APjAAAUrgpd8azOz/xOudCtMqLNBJddFnVGfg8ZCaz+o9OdWBuWoHI1m 07ZKNIxMsqqPco8q0+IYIit3A/grS3NkAMrKEdBX6Q== X-Google-Smtp-Source: APXvYqxvbX5HnbdxCxn0UkGL+A+x3MpHc4vy95/TcXNzuKlfBpKjmHOwVBhcsgnzOWyJjNgxBrlFywGyzVrnPfmB3R4= X-Received: by 2002:ab0:73d3:: with SMTP id m19mr22677431uaq.46.1554900996981; Wed, 10 Apr 2019 05:56:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 10 Apr 2019 14:56:25 +0200 Message-ID: To: =?UTF-8?B?UHJ6ZW15c8WCYXcgT8WCdGFyemV3c2tp?= Cc: Chas Williams <3chas3@gmail.com>, dev Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190410125625.kJPphB_xwGP2_jp28DsJBttiES4yD46BK0hi8Sx0OWY@z> On Wed, Apr 10, 2019 at 1:33 PM Przemys=C5=82aw O=C5=82tarzewski < p.oltarzewski@gmail.com> wrote: > Hello David, > > I can merge these fixes and run our system using patched DPDK version. > Then report back any problems / improvements I observe. I can also walk > through source code changes and check for anything questionable. > > Unfortunately I lack deep enough understanding of DPDK source code to tes= t > these fixes comprehensively and I have been short on time recently as wel= l, > so that's the best I can do right now. > Please, be aware that other fixes have been already merged in master since 18.11. https://git.dpdk.org/dpdk/log/drivers/net/bonding I just sent the patchset that should fix your issue: http://patchwork.dpdk.org/project/dpdk/list/?series=3D4240 --=20 David Marchand