From: David Marchand <david.marchand@redhat.com>
To: Xueming Li <xuemingl@nvidia.com>
Cc: dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>,
Gaetan Rivet <grive@u256.net>,
vijay.srivastava@xilinx.com
Subject: Re: [dpdk-stable] [PATCH v1] eal: fix random device arguments in device iterator
Date: Thu, 4 Nov 2021 11:41:50 +0100 [thread overview]
Message-ID: <CAJFAV8yFSVrp7be7aLDQzgMdihFaJfj+fSn2jXsXu1eCuo+jnw@mail.gmail.com> (raw)
In-Reply-To: <20211027082221.693957-1-xuemingl@nvidia.com>
On Wed, Oct 27, 2021 at 10:23 AM Xueming Li <xuemingl@nvidia.com> wrote:
>
> Devargs used in device iterator initialization wasn't set to zero, random
> data like bus string lead to invalid address access.
>
> This patch initializes devargs.
>
> Fixes: c99a2d4c6b7f ("eal: implement device iteration initialization")
> Cc: stable@dpdk.org
>
> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
Applied, thanks.
It seems a basic issue, could it be caught with a unit test?
Thanks.
--
David Marchand
prev parent reply other threads:[~2021-11-04 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 8:22 Xueming Li
2021-11-04 10:41 ` David Marchand [this message]
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=CAJFAV8yFSVrp7be7aLDQzgMdihFaJfj+fSn2jXsXu1eCuo+jnw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=stable@dpdk.org \
--cc=vijay.srivastava@xilinx.com \
--cc=xuemingl@nvidia.com \
/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).