qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Stefan Weil <sw@weilnetz.de>, QEMU Trivial <qemu-trivial@nongnu.org>
Cc: QEMU Developer <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] pci-assign: Fix warning from coverity (argument cannot be negative)
Date: Sat, 14 Mar 2015 18:23:33 +0800	[thread overview]
Message-ID: <55040C25.7010706@huawei.com> (raw)
In-Reply-To: <1426323477-949-1-git-send-email-sw@weilnetz.de>

On 2015/3/14 16:57, Stefan Weil wrote:
> Coverity warns because function monitor_fd_param can return a negative
> value which might be passed to function read.
> 
> This won't happen because dev->config_fd will only be negative (-1)
> when local_err is set.

Yes.

> 
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
>  hw/i386/kvm/pci-assign.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/i386/kvm/pci-assign.c b/hw/i386/kvm/pci-assign.c
> index 9db7c77..f3d145b 100644
> --- a/hw/i386/kvm/pci-assign.c
> +++ b/hw/i386/kvm/pci-assign.c
> @@ -554,7 +554,7 @@ static void get_real_device(AssignedDevice *pci_dev, Error **errp)
>      if (pci_dev->configfd_name && *pci_dev->configfd_name) {
>          dev->config_fd = monitor_fd_param(cur_mon, pci_dev->configfd_name,
>                                            &local_err);
> -        if (local_err) {
> +        if (dev->config_fd < 0) {
>              error_propagate(errp, local_err);
>              return;
>          }
> 

This fix the coverity warning of dev->config_id. I'm not sure that this may introduce
another warning of not checking local_err.

-- 
Thanks,
Shannon

      reply	other threads:[~2015-03-14 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14  8:57 [Qemu-devel] [PATCH] pci-assign: Fix warning from coverity (argument cannot be negative) Stefan Weil
2015-03-14 10:23 ` Shannon Zhao [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=55040C25.7010706@huawei.com \
    --to=zhaoshenglong@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).