From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 0/4] Fixes for coverity issues in fbarray
Date: Mon, 23 Apr 2018 22:16:38 +0200 [thread overview]
Message-ID: <3940059.fMP8snkLnf@xps> (raw)
In-Reply-To: <20180418085139.GN4957@6wind.com>
18/04/2018 10:51, Adrien Mazarguil:
> 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>
Applied, thanks
prev parent reply other threads:[~2018-04-23 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 15:44 Anatoly Burakov
2018-04-17 15:44 ` [dpdk-dev] [PATCH 1/4] fbarray: use strlcpy instead of snprintf Anatoly Burakov
2018-04-17 15:44 ` [dpdk-dev] [PATCH 2/4] fbarray: add check for failed file descriptor open Anatoly Burakov
2018-04-17 15:44 ` [dpdk-dev] [PATCH 3/4] fbarray: fix potential null-dereference Anatoly Burakov
2018-04-17 15:44 ` [dpdk-dev] [PATCH 4/4] fbarray: handle negative return Anatoly Burakov
2018-04-18 8:51 ` [dpdk-dev] [PATCH 0/4] Fixes for coverity issues in fbarray Adrien Mazarguil
2018-04-23 20:16 ` Thomas Monjalon [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=3940059.fMP8snkLnf@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=anatoly.burakov@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).