Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/5] Add error handling for add and del commands
Date: Tue,  9 Oct 2018 19:52:02 +0900	[thread overview]
Message-ID: <20181009105207.42636-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)

From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

There is no strict checking for returned value of parsing resource UID
for add and del commands. It might cause a fatal error if no existing
resource is accessed for inappropriate resource UID.

To avoid inappropriate accessing, add checking for the resource UID and
correct determining of the returned value. This update also includes
refactors of log messages in add_ring_pmd() to create a ring port
correctly.

Yasufumi Ogawa (5):
  shared: add error handling for invalid res UID
  spp_nfv: add error handling for add and del cmd
  spp_vm: add error handling for add and del cmd
  spp_nfv: refactor add_ring_pmd
  spp_vm: refactor add_ring_pmd

 src/nfv/nfv.c       | 66 ++++++++++++++++++++++++++++++++++++-----------------
 src/shared/common.c |  7 ++++++
 src/vm/main.c       | 57 +++++++++++++++++++++++++++++++--------------
 3 files changed, 92 insertions(+), 38 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-10-09 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 10:52 ogawa.yasufumi [this message]
2018-10-09 10:52 ` [spp] [PATCH 1/5] shared: add error handling for invalid res UID ogawa.yasufumi
2018-10-09 10:52 ` [spp] [PATCH 2/5] spp_nfv: add error handling for add and del cmd ogawa.yasufumi
2018-10-09 10:52 ` [spp] [PATCH 3/5] spp_vm: " ogawa.yasufumi
2018-10-09 10:52 ` [spp] [PATCH 4/5] spp_nfv: refactor add_ring_pmd ogawa.yasufumi
2018-10-09 10:52 ` [spp] [PATCH 5/5] spp_vm: " ogawa.yasufumi

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=20181009105207.42636-1-ogawa.yasufumi@lab.ntt.co.jp \
    --to=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=ferruh.yigit@intel.com \
    --cc=spp@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).