From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Li Qiang <liq3ea@gmail.com>,
Wolfgang Bumiller <w.bumiller@proxmox.com>,
Li Qiang <liqiang6-s@360.cn>,
ghoffman@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] cirrus: fix oob access issue
Date: Wed, 25 Jan 2017 08:26:02 +0100 [thread overview]
Message-ID: <1485329162.29826.19.camel@redhat.com> (raw)
In-Reply-To: <4623f4c5-e075-38f4-897d-00002392f8b2@redhat.com>
Hi,
> > I have read all the discuss, very long and useful, but I think I still
> > need some
> > time to get a full understand. So I think one of you can provide the
> > formal patch to
> > describe the issue in more detail.
>
> Your patch is almost correct.
New version out for review.
> Gerd, do you think you can raise this with the SRT? (I mean, if you
> agree that this is a security issue.)
Yes, it is. Getting a CVE number for it is wip.
cheers,
Gerd
next prev parent reply other threads:[~2017-01-25 7:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 9:34 [Qemu-devel] [PATCH] cirrus: fix oob access issue Li Qiang
2017-01-24 9:50 ` no-reply
2017-01-24 10:23 ` Laszlo Ersek
2017-01-24 10:48 ` Gerd Hoffmann
2017-01-24 11:17 ` Laszlo Ersek
2017-01-24 11:24 ` Laszlo Ersek
2017-01-24 12:29 ` Gerd Hoffmann
2017-01-24 15:31 ` Wolfgang Bumiller
2017-01-24 16:12 ` Laszlo Ersek
2017-01-25 1:18 ` Li Qiang
2017-01-25 3:31 ` Laszlo Ersek
2017-01-25 7:26 ` Gerd Hoffmann [this message]
2017-01-25 7:18 ` Gerd Hoffmann
2017-01-25 10:13 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2017-01-24 9:58 Li Qiang
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=1485329162.29826.19.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=ghoffman@redhat.com \
--cc=lersek@redhat.com \
--cc=liq3ea@gmail.com \
--cc=liqiang6-s@360.cn \
--cc=qemu-devel@nongnu.org \
--cc=w.bumiller@proxmox.com \
/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.