qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@iki.fi>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: assert that target_mprotect cannot fail
Date: Thu, 1 Oct 2015 11:46:29 +0300	[thread overview]
Message-ID: <20151001084629.GA8991@kos.to> (raw)
In-Reply-To: <1442226704-29349-1-git-send-email-pbonzini@redhat.com>

On Mon, Sep 14, 2015 at 12:31:44PM +0200, Paolo Bonzini wrote:
> All error conditions that target_mprotect checks are also checked
> by target_mmap.  EACCESS cannot happen because we are just removing
> PROT_WRITE.  ENOMEM should not happen because we are modifying a
> whole VMA (and we have bigger problems anyway if it happens).
> 
> Fixes a Coverity false positive, where Coverity complains about
> target_mprotect's return value being passed to tb_invalidate_phys_range.

Applied to linux-user, thanks

> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  linux-user/mmap.c | 5 +----
>  1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/linux-user/mmap.c b/linux-user/mmap.c
> index b2126c7..5606bcd 100644
> --- a/linux-user/mmap.c
> +++ b/linux-user/mmap.c
> @@ -514,10 +514,7 @@ abi_long target_mmap(abi_ulong start, abi_ulong len, int prot,
>                  goto fail;
>              if (!(prot & PROT_WRITE)) {
>                  ret = target_mprotect(start, len, prot);
> -                if (ret != 0) {
> -                    start = ret;
> -                    goto the_end;
> -                }
> +                assert(ret == 0);
>              }
>              goto the_end;
>          }
> -- 
> 2.5.0
> 
> 

      reply	other threads:[~2015-10-01  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 10:31 [Qemu-devel] [PATCH] linux-user: assert that target_mprotect cannot fail Paolo Bonzini
2015-10-01  8:46 ` Riku Voipio [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=20151001084629.GA8991@kos.to \
    --to=riku.voipio@iki.fi \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).