From: Olivier Matz <olivier.matz@6wind.com>
To: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] cmdline: fix unchecked return value
Date: Mon, 2 May 2016 15:37:06 +0200 [thread overview]
Message-ID: <57275802.7090606@6wind.com> (raw)
In-Reply-To: <1460638879-45680-1-git-send-email-danielx.t.mrzyglod@intel.com>
Hi Daniel,
On 04/14/2016 03:01 PM, Daniel Mrzyglod wrote:
> This patch is for checking if error values occurs.
> fix for coverity errors #13209 & #13195
>
> If the function returns an error value, the error value may be mistaken
> for a normal value.
>
> In rdline_char_in: Value returned from a function is not checked for errors
> before being used
>
> Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
> ---
> lib/librte_cmdline/cmdline_rdline.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/lib/librte_cmdline/cmdline_rdline.c b/lib/librte_cmdline/cmdline_rdline.c
> index 1ef2258..e75a556 100644
> --- a/lib/librte_cmdline/cmdline_rdline.c
> +++ b/lib/librte_cmdline/cmdline_rdline.c
> @@ -377,7 +377,10 @@ rdline_char_in(struct rdline *rdl, char c)
> case CMDLINE_KEY_CTRL_K:
> cirbuf_get_buf_head(&rdl->right, rdl->kill_buf, RDLINE_BUF_SIZE);
> rdl->kill_size = CIRBUF_GET_LEN(&rdl->right);
> - cirbuf_del_buf_head(&rdl->right, rdl->kill_size);
> +
> + if (cirbuf_del_buf_head(&rdl->right, rdl->kill_size) < 0)
> + return -EINVAL;
> +
> rdline_puts(rdl, vt100_clear_right);
> break;
>
I wonder if a better way to fix wouldn't be to remove the checks
introduced in http://dpdk.org/browse/dpdk/commit/?id=ab971e562860
There is no reason to check that in cirbuf_get_buf_head/tail():
if (!cbuf || !c)
The function should never fail, it just returns the number of
copied chars. This is the responsibility of the caller to ensure
that the pointer to the circular buffer is not NULL.
Also, rdline_char_in() is not expected to return -EINVAL, but
RDLINE_RES_* instead.
So I think that partially revert ab971e562860 would fix the
coverity warning.
Regards,
Olivier
next prev parent reply other threads:[~2016-05-02 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 13:01 Daniel Mrzyglod
2016-05-02 13:37 ` Olivier Matz [this message]
2016-06-28 9:49 ` Mrzyglod, DanielX T
2016-07-01 7:19 ` Olivier MATZ
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=57275802.7090606@6wind.com \
--to=olivier.matz@6wind.com \
--cc=danielx.t.mrzyglod@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).