From: Aaron Conole <aconole@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix check for default plugin directory
Date: Mon, 06 Nov 2017 15:36:46 -0500 [thread overview]
Message-ID: <f7t1slbi1pd.fsf@dhcp-25-97.bos.redhat.com> (raw)
In-Reply-To: <20171106135800.12350-1-bruce.richardson@intel.com> (Bruce Richardson's message of "Mon, 6 Nov 2017 13:58:00 +0000")
Bruce Richardson <bruce.richardson@intel.com> writes:
> The check for the existence of the default plugin directory calls stat
> using an incorrect variable, which will cause a NULL pointer dereference
> error.
>
> Coverity issue: 198440
> Fixes: d6a4399cdfc9 ("eal: avoid error for non-existent default PMD path")
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
Acked-by: Aaron Conole <aconole@redhat.com>
Glad I checked the list before going after this one. ;)
next prev parent reply other threads:[~2017-11-06 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 13:58 Bruce Richardson
2017-11-06 20:36 ` Aaron Conole [this message]
2017-11-07 0:23 ` 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=f7t1slbi1pd.fsf@dhcp-25-97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=bruce.richardson@intel.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).