From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: bernard.iremonger@intel.com,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH] reorder: add checks for invalid function inputs
Date: Wed, 10 Apr 2019 12:24:47 +0100 [thread overview]
Message-ID: <20190410112447.68386-1-bruce.richardson@intel.com> (raw)
Message-ID: <20190410112447.p-E0P-s0H_EAZ6uHCRtQDlHCdxFlcoqdAeDSJeZxKz4@z> (raw)
For APIs which can return an error value, do sanity checking of the input
parameters for NULL and return a suitable error value for those cases.
NOTE: The drain function is currently omitting NULL checks too, but this
function has no way to flag an error value, so checking in that case would
simply mask problems.
Reported-by: Bernard Iremonger <bernard.iremonger@intel.com>
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
lib/librte_reorder/rte_reorder.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/lib/librte_reorder/rte_reorder.c b/lib/librte_reorder/rte_reorder.c
index b15328b2e..3a4a1b0a0 100644
--- a/lib/librte_reorder/rte_reorder.c
+++ b/lib/librte_reorder/rte_reorder.c
@@ -222,6 +222,11 @@ rte_reorder_find_existing(const char *name)
struct rte_tailq_entry *te;
struct rte_reorder_list *reorder_list;
+ if (name == NULL) {
+ rte_errno = EINVAL;
+ return NULL;
+ }
+
reorder_list = RTE_TAILQ_CAST(rte_reorder_tailq.head, rte_reorder_list);
rte_rwlock_read_lock(RTE_EAL_TAILQ_RWLOCK);
@@ -295,8 +300,14 @@ int
rte_reorder_insert(struct rte_reorder_buffer *b, struct rte_mbuf *mbuf)
{
uint32_t offset, position;
- struct cir_buffer *order_buf = &b->order_buf;
+ struct cir_buffer *order_buf;
+
+ if (b == NULL || mbuf == NULL) {
+ rte_errno = EINVAL;
+ return -1;
+ }
+ order_buf = &b->order_buf;
if (!b->is_initialized) {
b->min_seqn = mbuf->seqn;
b->is_initialized = 1;
--
2.20.1
next reply other threads:[~2019-04-10 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 11:24 Bruce Richardson [this message]
2019-04-10 11:24 ` Bruce Richardson
2019-04-11 8:43 ` Iremonger, Bernard
2019-04-11 8:43 ` Iremonger, Bernard
2019-04-22 17:37 ` Thomas Monjalon
2019-04-22 17:37 ` 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=20190410112447.68386-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=bernard.iremonger@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).