From: "Gaëtan Rivet" <grive@u256.net>
To: "David Marchand" <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>,
"madhuker.mythri" <madhuker.mythri@oracle.com>,
"Ferruh Yigit" <ferruh.yigit@intel.com>
Subject: Re: [PATCH] devargs: Fix rte_devargs_parse uninitialized calls
Date: Wed, 16 Feb 2022 18:12:40 +0100 [thread overview]
Message-ID: <056a903d-ae14-419c-85d4-f512dc239d9b@www.fastmail.com> (raw)
In-Reply-To: <CAJFAV8wncjPReH1etvkpQst8J6U1iaZs0dkbfA0r_ZvpYMZvhw@mail.gmail.com>
On Tue, Feb 15, 2022, at 16:27, David Marchand wrote:
> On Thu, Feb 10, 2022 at 6:01 PM Gaetan Rivet <grive@u256.net> wrote:
>>
>> The function rte_devargs_parse() previously was safe to call with
>> non-initialized devargs structure as parameter.
>>
>> When adding the support for the global device syntax,
>> this assumption was broken. Restore it by forcing memset as part of
>> the call itself.
>>
>> Bugzilla Id: 933
>
> Nit: Bugzilla ID*
>
>> Fixes: b344eb5d941a ("devargs: parse global device syntax")
>
> We need a backport in 21.11, right?
Hi David, yes it should be in 21.11 as well.
--
Gaetan Rivet
prev parent reply other threads:[~2022-02-16 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:10 [PATCH] net/failsafe: Fix crash due to global devargs syntax parsing from secondary process madhuker.mythri
2022-02-10 15:00 ` Ferruh Yigit
2022-02-10 16:08 ` Gaëtan Rivet
2022-02-11 9:37 ` [External] : Re: Madhuker Mythri
2022-02-11 9:58 ` [External] : Re: [PATCH] net/failsafe: Fix crash due to global devargs syntax parsing from secondary process Ferruh Yigit
2022-02-11 9:58 ` [External] : Gaëtan Rivet
2022-02-16 8:27 ` Long Li
2022-02-10 17:01 ` [PATCH] devargs: Fix rte_devargs_parse uninitialized calls Gaetan Rivet
2022-02-15 12:51 ` Ferruh Yigit
2022-02-15 13:45 ` Gaëtan Rivet
2022-02-15 15:27 ` David Marchand
2022-02-16 17:12 ` Gaëtan Rivet [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=056a903d-ae14-419c-85d4-f512dc239d9b@www.fastmail.com \
--to=grive@u256.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=madhuker.mythri@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.