All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike McCormack <mj.mccormack@samsung.com>
To: qemu-devel@nongnu.org
Cc: stefanha@gmail.com, riku.voipio@nokia.com, vapier@gentoo.org
Subject: [Qemu-devel] [PATCH] Don't zero out buffer in sched_getaffinity
Date: Mon, 18 Apr 2011 16:03:59 +0900	[thread overview]
Message-ID: <4DABE25F.8000203@samsung.com> (raw)

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

Depends on sched_getaffinity buffer overrun fix, but submitted
separately to make rollback easier.

---
 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 19209a2..e2a5fd9 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -6382,20 +6382,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-18  7:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18  7:03 Mike McCormack [this message]
2011-04-18  9:17 ` [Qemu-devel] [PATCH] Don't zero out buffer in sched_getaffinity Stefan Hajnoczi

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=4DABE25F.8000203@samsung.com \
    --to=mj.mccormack@samsung.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@nokia.com \
    --cc=stefanha@gmail.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.