From: "Przemysław Ołtarzewski" <p.oltarzewski@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Chas Williams <3chas3@gmail.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [Bug 248] Bonding PMD: Invalid array dimension in TX burst for 802.3ad mode with fast queue leads to SEGFAULT
Date: Mon, 15 Apr 2019 11:50:35 +0200 [thread overview]
Message-ID: <CAFJX8XjvATKzCfscJHjVVvxgTyEa_h7CovjDu5fTUq3rXH0Jsw@mail.gmail.com> (raw)
Message-ID: <20190415095035.X24l4Xy1zAzBB4wMminmfY2lqDwFgE7UUvZnvS1qFQM@z> (raw)
In-Reply-To: <CAJFAV8z5q=fSPXj7t9yA=VbcVhHmV08G4q7_27pAQb3q2B9TYw@mail.gmail.com>
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.
Best Regards,
Przemysław Ołtarzewski
On Wed, Apr 10, 2019 at 2:56 PM David Marchand <david.marchand@redhat.com>
wrote:
> On Wed, Apr 10, 2019 at 1:33 PM Przemysław Ołtarzewski <
> 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
>> test these fixes comprehensively and I have been short on time recently as
>> well, 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=4240
>
>
> --
> David Marchand
>
next prev parent reply other threads:[~2019-04-16 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 14:44 bugzilla
2019-04-09 14:44 ` bugzilla
2019-04-09 14:51 ` David Marchand
2019-04-09 14:51 ` David Marchand
2019-04-10 11:39 ` Przemysław Ołtarzewski
2019-04-10 11:39 ` Przemysław Ołtarzewski
2019-04-10 12:56 ` David Marchand
2019-04-10 12:56 ` David Marchand
2019-04-15 9:50 ` Przemysław Ołtarzewski [this message]
2019-04-15 9:50 ` Przemysław Ołtarzewski
2019-04-18 9:38 ` Kevin Traynor
2019-04-18 9:38 ` Kevin Traynor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFJX8XjvATKzCfscJHjVVvxgTyEa_h7CovjDu5fTUq3rXH0Jsw@mail.gmail.com \
--to=p.oltarzewski@gmail.com \
--cc=3chas3@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).