From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, thomas@monjalon.net
Subject: Re: [PATCH 0/4] Fixes for coverity issues in fbarray
Date: Wed, 18 Apr 2018 10:51:39 +0200 [thread overview]
Message-ID: <20180418085139.GN4957@6wind.com> (raw)
In-Reply-To: <cover.1523978190.git.anatoly.burakov@intel.com>
On Tue, Apr 17, 2018 at 04:44:04PM +0100, Anatoly Burakov wrote:
> This patchset fixes a number of Coverity issues introduced
> in recent DPDK memory hotplug patchset.
>
> Coverity issues fixed:
> - 272564 - error condition not checked
> - 272579 - dereference before null check
> - 272586 - error condition not checked
>
> There are two additional issues reported by coverity:
> - 272598 - error condition not checked
> - 272599 - error condition not checked
>
> However, they are fixed by a separate patch [1].
>
> [1] http://dpdk.org/dev/patchwork/patch/38091/
>
> Anatoly Burakov (4):
> fbarray: use strlcpy instead of snprintf
> fbarray: add check for failed file descriptor open
> fbarray: fix potential null-dereference
> fbarray: handle negative return
Given that I recently addressed a similar issue in fbarray as well:
Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2018-04-18 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 15:44 [PATCH 0/4] Fixes for coverity issues in fbarray Anatoly Burakov
2018-04-17 15:44 ` [PATCH 1/4] fbarray: use strlcpy instead of snprintf Anatoly Burakov
2018-04-17 15:44 ` [PATCH 2/4] fbarray: add check for failed file descriptor open Anatoly Burakov
2018-04-17 15:44 ` [PATCH 3/4] fbarray: fix potential null-dereference Anatoly Burakov
2018-04-17 15:44 ` [PATCH 4/4] fbarray: handle negative return Anatoly Burakov
2018-04-18 8:51 ` Adrien Mazarguil [this message]
2018-04-23 20:16 ` [PATCH 0/4] Fixes for coverity issues in fbarray 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=20180418085139.GN4957@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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.