From: Stefan Hajnoczi <stefanha@gmail.com>
To: Mike McCormack <mj.mccormack@samsung.com>
Cc: riku.voipio@nokia.com, vapier@gentoo.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Don't zero out buffer in sched_getaffinity
Date: Mon, 18 Apr 2011 10:17:25 +0100 [thread overview]
Message-ID: <BANLkTincBg6OfWLrfRVTVEhq3fG0iWcLOw@mail.gmail.com> (raw)
In-Reply-To: <4DABE25F.8000203@samsung.com>
On Mon, Apr 18, 2011 at 8:03 AM, Mike McCormack
<mj.mccormack@samsung.com> wrote:
> 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(-)
Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
prev parent reply other threads:[~2011-04-18 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 7:03 [Qemu-devel] [PATCH] Don't zero out buffer in sched_getaffinity Mike McCormack
2011-04-18 9:17 ` Stefan Hajnoczi [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=BANLkTincBg6OfWLrfRVTVEhq3fG0iWcLOw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=mj.mccormack@samsung.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@nokia.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 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).