From: Luiz Capitulino <lcapitulino@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: peter.maydell@linaro.org, aliguori@us.ibm.com,
mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] qga umask fix addenda
Date: Fri, 10 May 2013 09:29:50 -0400 [thread overview]
Message-ID: <20130510092950.1d3d79e6@redhat.com> (raw)
In-Reply-To: <1368027096-12108-1-git-send-email-lersek@redhat.com>
On Wed, 8 May 2013 17:31:34 +0200
Laszlo Ersek <lersek@redhat.com> wrote:
> I should have paid more attention to portability and error path cleanup
> in the CVE-2013-2007 fix.
>
> (We continue to assume, like the rest of qemu code, that
> qemu_set_cloexec() never fails internally. This should be a reasonable
> assumption when the input fd is valid.)
Series:
Reviewed-by: Luiz Capitulino <lcapitulino@redhat.com>
>
> Laszlo Ersek (2):
> qga: distinguish binary modes in "guest_file_open_modes" map
> qga: unlink just created guest-file if fchmod() or fdopen() fails on
> it
>
> qga/commands-posix.c | 25 +++++++++++++++++++------
> 1 files changed, 19 insertions(+), 6 deletions(-)
>
>
next prev parent reply other threads:[~2013-05-10 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 15:31 [Qemu-devel] [PATCH v2 0/2] qga umask fix addenda Laszlo Ersek
2013-05-08 15:31 ` [Qemu-devel] [PATCH v2 1/2] qga: distinguish binary modes in "guest_file_open_modes" map Laszlo Ersek
2013-05-08 15:31 ` [Qemu-devel] [PATCH v2 2/2] qga: unlink just created guest-file if fchmod() or fdopen() fails on it Laszlo Ersek
2013-05-08 17:07 ` Eric Blake
2013-05-10 13:29 ` Luiz Capitulino [this message]
2013-05-10 19:30 ` [Qemu-devel] [PATCH v2 0/2] qga umask fix addenda mdroth
2013-05-10 19:53 ` Laszlo Ersek
2013-05-10 20:09 ` mdroth
2013-05-12 16:47 ` Andreas Färber
2013-05-13 11:33 ` mdroth
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=20130510092950.1d3d79e6@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=lersek@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--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).