Re: [PATCH] devargs: Fix rte_devargs_parse uninitialized calls

2022-02-16 Thread Gaëtan Rivet
On Tue, Feb 15, 2022, at 16:27, David Marchand wrote: > On Thu, Feb 10, 2022 at 6:01 PM Gaetan Rivet 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

Re: [PATCH] devargs: Fix rte_devargs_parse uninitialized calls

2022-02-15 Thread David Marchand
On Thu, Feb 10, 2022 at 6:01 PM Gaetan Rivet 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 o

Re: [PATCH] devargs: Fix rte_devargs_parse uninitialized calls

2022-02-15 Thread Gaëtan Rivet
On Tue, Feb 15, 2022, at 13:51, Ferruh Yigit wrote: > On 2/10/2022 5:01 PM, Gaetan Rivet 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

Re: [PATCH] devargs: Fix rte_devargs_parse uninitialized calls

2022-02-15 Thread Ferruh Yigit
On 2/10/2022 5:01 PM, Gaetan Rivet 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.