qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: riku.voipio@linaro.org
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Riku Voipio <riku.voipio@linaro.org>
Subject: [Qemu-devel] [PATCH] linux-user: don't warn on missing capget/capset
Date: Mon, 17 Mar 2014 13:55:31 +0200	[thread overview]
Message-ID: <1395057331-12329-1-git-send-email-riku.voipio@linaro.org> (raw)

From: Riku Voipio <riku.voipio@linaro.org>

some people get numerous unimplemented capget/capset warnings. Since qemu
linux-user is not secure to begin with, just skip the system call
warning for now. Proper capset/capget to be added in Qemu 2.1

Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
---
 linux-user/syscall.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index e404a32..4bfa3db 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -7677,9 +7677,9 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
         unlock_user(p, arg1, ret);
         break;
     case TARGET_NR_capget:
-        goto unimplemented;
+        goto unimplemented_nowarn;
     case TARGET_NR_capset:
-        goto unimplemented;
+        goto unimplemented_nowarn;
     case TARGET_NR_sigaltstack:
 #if defined(TARGET_I386) || defined(TARGET_ARM) || defined(TARGET_MIPS) || \
     defined(TARGET_SPARC) || defined(TARGET_PPC) || defined(TARGET_ALPHA) || \
-- 
1.8.5.3

             reply	other threads:[~2014-03-17 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 11:55 riku.voipio [this message]
2014-03-17 20:17 ` [Qemu-devel] [PATCH] linux-user: don't warn on missing capget/capset Andreas Färber
2014-03-18  6:22   ` Riku Voipio

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=1395057331-12329-1-git-send-email-riku.voipio@linaro.org \
    --to=riku.voipio@linaro.org \
    --cc=peter.maydell@linaro.org \
    --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).