From: "Wodkowski, PawelX" <pawelx.wodkowski@intel.com>
To: "Doherty, Declan" <declan.doherty@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] bond: static analysis issues fix
Date: Tue, 16 Dec 2014 08:50:40 +0000 [thread overview]
Message-ID: <F6F2A6264E145F47A18AB6DF8E87425D12B7A55F@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1418663630-27409-1-git-send-email-declan.doherty@intel.com>
> -----Original Message-----
> From: Doherty, Declan
> Sent: Monday, December 15, 2014 6:14 PM
> To: dev@dpdk.org
> Cc: Wodkowski, PawelX; Doherty, Declan
> Subject: [PATCH v2] bond: static analysis issues fix
>
> -v2:
> Incorporates Pawel's comments regarding assertion's check on activate_slave
> array indexing
>
> Fixes for link bonding library identified by static analysis tool
>
> - Overflow assert for active_slaves array in activate_slave function
> - Allocation check of pci_id_table in rte_eth_bond_create
> - Use of eth_dev pointer in mac_address_get/set before NULL check
>
> Signed-off-by: Declan Doherty <declan.doherty@intel.com>
> ---
>
Acked-by: Wodkowski, Pawel <pawelx.wodkowski@intel.com>
next prev parent reply other threads:[~2014-12-16 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 17:39 [dpdk-dev] [PATCH] " Declan Doherty
2014-12-12 18:30 ` Wodkowski, PawelX
2014-12-15 17:13 ` [dpdk-dev] [PATCH v2] " Declan Doherty
2014-12-16 8:50 ` Wodkowski, PawelX [this message]
2014-12-16 17:31 ` Thomas Monjalon
2014-12-17 11:46 ` [dpdk-dev] [PATCH v3 0/3] " Declan Doherty
2014-12-17 11:46 ` [dpdk-dev] [PATCH v3 1/3] bond: add bounds check before assigning active slave count value Declan Doherty
2014-12-17 11:46 ` [dpdk-dev] [PATCH v3 2/3] bond: fix pci_id_table allocation check in rte_eth_bond_create Declan Doherty
2014-12-17 11:46 ` [dpdk-dev] [PATCH v3 3/3] bond: eth_dev parameter used before NULL check in mac_address_get/set Declan Doherty
2014-12-17 23:43 ` [dpdk-dev] [PATCH v3 0/3] bond: static analysis issues fix 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=F6F2A6264E145F47A18AB6DF8E87425D12B7A55F@IRSMSX102.ger.corp.intel.com \
--to=pawelx.wodkowski@intel.com \
--cc=declan.doherty@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).