DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Cunming Liang <cunming.liang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] eal: fix negative value incorrectly being used defect
Date: Sat, 12 Dec 2015 22:03:15 +0100	[thread overview]
Message-ID: <10010035.bssIcGskrK@xps13> (raw)
In-Reply-To: <CALwxeUtCJzsVCSuQR=U9CCs63vWJ9LiYzgEDwE=K_proU1QOsA@mail.gmail.com>

2015-12-11 15:54, David Marchand:
> Hello Cunming,
> 
> On Fri, Dec 11, 2015 at 2:48 AM, Cunming Liang <cunming.liang@intel.com>
> wrote:
> 
> > In eal_intr_proc_rxtx_intr, negative value may be used as argument to a
> > function expecting a positive value. If 'read' returns EAGAIN as example,
> > the bytes_read updates to a negative value which continue be passed as
> > argument for the next 'read'.
> >
> > Coverity issue: 107115
> >
> > 927        do {
> >     3. negative_return_fn: Function read(fd, &buf, bytes_read) returns a
> > negative number.
> >     4. var_assign: Assigning: signed variable bytes_read = read.
> >     CID 107115 (#1 of 1): Argument cannot be negative
> >     (NEGATIVE_RETURNS)9. negative_returns: bytes_read is passed to a
> > parameter
> >     that cannot be negative.
> > 928                bytes_read = read(fd, &buf, bytes_read);
> >
> > Fixes: c9f3ec1a0f3f ("eal/linux: add Rx interrupt control function")
> >
> > Signed-off-by: Cunming Liang <cunming.liang@intel.com>
> >
> 
> Acked-by: David Marchand <david.marchand@6wind.com>

Applied, thanks

      reply	other threads:[~2015-12-12 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  1:48 Cunming Liang
2015-12-11 14:40 ` Mcnamara, John
2015-12-11 14:54 ` David Marchand
2015-12-12 21:03   ` 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=10010035.bssIcGskrK@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=cunming.liang@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).