From: Gerd Hoffmann <kraxel@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: d@vidbuchanan.co.uk, P J P <ppandit@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] vga: stop passing pointers to vga_draw_line* functions
Date: Fri, 25 Aug 2017 13:22:46 +0200 [thread overview]
Message-ID: <1503660166.9107.6.camel@redhat.com> (raw)
In-Reply-To: <cd7ebf5c-6d81-6cdf-f6b2-87af4cb00f85@redhat.com>
Hi,
> s/simliar/similar/
> s/priviledged/privileged/
Fixed.
> > a segfault, when hitting the guard page after vga memory
> > allocation, while reading vga memory for display updates.
> >
> > Fixes: CVE-2017-xxxx
>
> Do we have the actual number?
Not yet, pjp still busy getting one, but will be filled for the final
version of the patch.
> Are we trying to get this in 2.10-rc4, or
> is it merely 2.11 + qemu-stable (2.10.1) material?
IMO it isn't critical enough to squeeze the non-trivial patch into 2.10
the last minute, so qemu-stable.
cheers,
Gerd
next prev parent reply other threads:[~2017-08-25 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 9:19 [Qemu-devel] [PATCH] vga: stop passing pointers to vga_draw_line* functions Gerd Hoffmann
2017-08-24 16:30 ` Eric Blake
2017-08-25 11:22 ` Gerd Hoffmann [this message]
2017-08-28 10:29 ` P J P
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=1503660166.9107.6.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=d@vidbuchanan.co.uk \
--cc=eblake@redhat.com \
--cc=ppandit@redhat.com \
--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).