From: Steven Haigh <netwiz@crc.id.au>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
M A Young <m.a.young@durham.ac.uk>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
security@xenproject.org
Subject: Re: Xen 4.5.1 released
Date: Tue, 23 Jun 2015 20:54:42 +1000 [thread overview]
Message-ID: <55893AF2.1030107@crc.id.au> (raw)
In-Reply-To: <21897.14550.293801.83425@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 813 bytes --]
On 23/06/2015 8:45 PM, Ian Jackson wrote:
> Ian Jackson writes ("Re: [Xen-devel] Xen 4.5.1 released"):
>> M A Young writes ("Re: [Xen-devel] Xen 4.5.1 released"):
>>> I don't believe this release has the qemu-xen-traditional half of XSA-135.
>>> If this wasn't deliberate it might be worth noting it somewhere.
>>
>> You're right. It appears that the patch for XSA-135 was never applied
>> to qemu-traditional, due to an oversight.
>
> The XSA-135 fix was missing everywhere. I have now applied it (to all
> trees 4.1 and onward).
Out of interest, is the plan now to re-release a fixed 4.5.1 archive or
document the lack of the XSA135 patches and allow people to patch manually?
--
Steven Haigh
Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-06-23 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 9:49 Xen 4.5.1 released Jan Beulich
2015-06-23 10:07 ` M A Young
2015-06-23 10:22 ` Ian Jackson
2015-06-23 10:45 ` Ian Jackson
2015-06-23 10:54 ` Steven Haigh [this message]
2015-06-23 12:37 ` Jan Beulich
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=55893AF2.1030107@crc.id.au \
--to=netwiz@crc.id.au \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=m.a.young@durham.ac.uk \
--cc=security@xenproject.org \
--cc=xen-devel@lists.xenproject.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.