From: "Wiles, Keith" <keith.wiles@intel.com>
To: David Marchand <david.marchand@6wind.com>,
"Wodkowski, PawelX" <pawelx.wodkowski@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: prevent dereferencing NULL pointer in rte_eal_devargs_add()
Date: Mon, 2 Mar 2015 14:40:09 +0000 [thread overview]
Message-ID: <D119D21B.158BA%keith.wiles@intel.com> (raw)
In-Reply-To: <CALwxeUuE1AjtZVpJrkJuXt6eGKEt97Rhi+-9OLC+=iuc+6FWWw@mail.gmail.com>
On 3/2/15, 6:23 AM, "David Marchand" <david.marchand@6wind.com> wrote:
>Hello Pawel,
>
>On Mon, Mar 2, 2015 at 12:09 PM, Pawel Wodkowski
><pawelx.wodkowski@intel.com
>> wrote:
>
>> On failure devargs->args should not be accesed if devargs is NULL.
>>
>
>accessed.
>
>
>>
>> Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com>
>> ---
>> lib/librte_eal/common/eal_common_devargs.c | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/lib/librte_eal/common/eal_common_devargs.c
>> b/lib/librte_eal/common/eal_common_devargs.c
>> index 9b110f7..615945e 100644
>> --- a/lib/librte_eal/common/eal_common_devargs.c
>> +++ b/lib/librte_eal/common/eal_common_devargs.c
>> @@ -124,12 +124,13 @@ rte_eal_devargs_add(enum rte_devtype devtype,
>>const
>> char *devargs_str)
>> return 0;
>>
>> fail:
>> - if (devargs->args)
>> - free(devargs->args);
>> if (buf)
>> free(buf);
>> - if (devargs)
>> + if (devargs) {
>> + free(devargs->args);
Do you not still need to check for args being NULL before calling free?
>> free(devargs);
>> + }
>> +
>> return -1;
>> }
>>
>>
>Fixes: c07691ae1089 ("devargs: remove limit on parameters length")
>Acked-by: David Marchand <david.marchand@6wind.com>
>
>--
>David Marchand
next prev parent reply other threads:[~2015-03-02 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 11:09 Pawel Wodkowski
2015-03-02 12:23 ` David Marchand
2015-03-02 14:40 ` Wiles, Keith [this message]
2015-03-02 14:55 ` Pawel Wodkowski
2015-03-02 16:47 ` Wiles, Keith
2015-03-02 17:35 ` Pawel Wodkowski
2015-03-02 18:39 ` Thomas Monjalon
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=D119D21B.158BA%keith.wiles@intel.com \
--to=keith.wiles@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=pawelx.wodkowski@intel.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).