All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
	qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, mrhines@us.ibm.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] RDMA: Fix error exits (for 2.4)
Date: Fri, 10 Jul 2015 23:10:21 +0200	[thread overview]
Message-ID: <55A034BD.90007@redhat.com> (raw)
In-Reply-To: <1436555332-19076-1-git-send-email-dgilbert@redhat.com>

Juan, okay for me to pick it up together with a bunch of other Coverity
fixes?

Paolo

On 10/07/2015 21:08, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> The error checks I added used 'break' after the error, but I'm
> in a switch inside the while loop, so they need to be 'goto out'.
> 
> Spotted by coverity; entries 1311368 and 1311369
> 
> Fixes: afcddefd
> 
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
>  migration/rdma.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/migration/rdma.c b/migration/rdma.c
> index f106b2a..74876fd 100644
> --- a/migration/rdma.c
> +++ b/migration/rdma.c
> @@ -2997,7 +2997,7 @@ static int qemu_rdma_registration_handle(QEMUFile *f, void *opaque)
>                               (unsigned int)comp->block_idx,
>                               rdma->local_ram_blocks.nb_blocks);
>                  ret = -EIO;
> -                break;
> +                goto out;
>              }
>              block = &(rdma->local_ram_blocks.block[comp->block_idx]);
>  
> @@ -3092,7 +3092,7 @@ static int qemu_rdma_registration_handle(QEMUFile *f, void *opaque)
>                                   (unsigned int)reg->current_index,
>                                   rdma->local_ram_blocks.nb_blocks);
>                      ret = -ENOENT;
> -                    break;
> +                    goto out;
>                  }
>                  block = &(rdma->local_ram_blocks.block[reg->current_index]);
>                  if (block->is_ram_block) {
> @@ -3102,7 +3102,7 @@ static int qemu_rdma_registration_handle(QEMUFile *f, void *opaque)
>                              block->block_name, block->offset,
>                              reg->key.current_addr);
>                          ret = -ERANGE;
> -                        break;
> +                        goto out;
>                      }
>                      host_addr = (block->local_host_addr +
>                                  (reg->key.current_addr - block->offset));
> @@ -3118,7 +3118,7 @@ static int qemu_rdma_registration_handle(QEMUFile *f, void *opaque)
>                              " chunk: %" PRIx64,
>                              block->block_name, reg->key.chunk);
>                          ret = -ERANGE;
> -                        break;
> +                        goto out;
>                      }
>                  }
>                  chunk_start = ram_chunk_start(block, chunk);
> 

  reply	other threads:[~2015-07-10 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 19:08 [Qemu-devel] [PATCH] RDMA: Fix error exits (for 2.4) Dr. David Alan Gilbert (git)
2015-07-10 21:10 ` Paolo Bonzini [this message]
2015-07-13  8:03   ` Juan Quintela

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=55A034BD.90007@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=mrhines@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.