All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike McCormack <mj.mccormack@samsung.com>
To: riku.voipio@iki.fi
Cc: Rafal Krypa <r.krypa@samsung.com>,
	vapier@gentoo.org, qemu-devel@nongnu.org,
	stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH 2/2] Don't zero out buffer in sched_getaffinity
Date: Tue, 19 Apr 2011 15:09:52 +0900	[thread overview]
Message-ID: <4DAD2730.5050803@samsung.com> (raw)

The kernel doesn't fill the buffer provided to sched_getaffinity
with zero bytes, so neither should QEMU.

Signed-off-by: Mike McCormack <mj.mccormack@samsung.com>
Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
---
 linux-user/syscall.c |   13 +------------
 1 files changed, 1 insertions(+), 12 deletions(-)

diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 1cda10a..e53b7e5 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -6384,20 +6384,9 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
             ret = get_errno(sys_sched_getaffinity(arg1, mask_size, mask));
 
             if (!is_error(ret)) {
-                if (arg2 > ret) {
-                    /* Zero out any extra space kernel didn't fill */
-                    unsigned long zero = arg2 - ret;
-                    p = alloca(zero);
-                    memset(p, 0, zero);
-                    if (copy_to_user(arg3 + ret, p, zero)) {
-                        goto efault;
-                    }
-                    arg2 = ret;
-                }
-                if (copy_to_user(arg3, mask, arg2)) {
+                if (copy_to_user(arg3, mask, ret)) {
                     goto efault;
                 }
-                ret = arg2;
             }
         }
         break;
-- 
1.7.0.4

                 reply	other threads:[~2011-04-19  6:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4DAD2730.5050803@samsung.com \
    --to=mj.mccormack@samsung.com \
    --cc=qemu-devel@nongnu.org \
    --cc=r.krypa@samsung.com \
    --cc=riku.voipio@iki.fi \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=vapier@gentoo.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 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.