xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: IAN DELANEY <della5@iinet.com.au>
Cc: xen-devel@lists.xen.org
Subject: Re: xen-CVE-2013-1442-XSA-62.patch
Date: Wed, 2 Oct 2013 17:59:05 +0100	[thread overview]
Message-ID: <524C50D9.2010902@citrix.com> (raw)
In-Reply-To: <20131003004744.711eaaae@archtester.homenetwork>

On 02/10/13 17:47, IAN DELANEY wrote:
> I am confused.
>
> http://xenbits.xen.org/xsa/advisory-62.html says 
>
> "Applying the attached patch resolves this issue.
>
> xsa62.patch                 Xen 4.2.x, 4.3.x, and unstable
> "
>         #Security patches
>         epatch "${FILESDIR}"/${PN}-4-CVE-2013-1918-XSA-45_[1-7].patch \
>                 "${FILESDIR}"/${PN}-4.2-2013-2076-XSA-52to54.patch \
>                 "${FILESDIR}"/${PN}-4.2-CVE-2013-1432-XSA-58.patch \
>                 "${FILESDIR}"/${PN}-CVE-2013-4355-XSA-63.patch \
>                 "${FILESDIR}"/${PN}-CVE-2013-4361-XSA-66.patch \
>                 "${FILESDIR}"/${PN}-CVE-2013-1442-XSA-62.patch
>
> in the ebuild yields
>
> * Applying
>   xen-4.2-2013-2076-XSA-52to54.patch ...
>   [ ok ]
>  * Applying
>   xen-4.2-CVE-2013-1432-XSA-58.patch ...
>   [ ok ]
>  * Applying
>   xen-CVE-2013-4355-XSA-63.patch ...
>   [ ok ]
>  * Applying
>   xen-CVE-2013-4361-XSA-66.patch ...
>   [ ok ]
>  * Applying xen-CVE-2013-1442-XSA-62.patch ...
>
>  * Failed Patch: xen-CVE-2013-1442-XSA-62.patch !
>  *
>    ( /home/testuser/cvsPortage/gentoo-x86/app-emulation/xen/files/xen-CVE-2013-1442-XSA-62.patch
>    )
>  * 
>  * Include in your bugreport the contents of:
>  * 
>  *   /mnt/gen2/TmpDir/portage/app-emulation/xen-4.2.2-r2/temp/xen-CVE-2013-1442-XSA-62.patch.out
>
>  * ERROR: app-emulation/xen-4.2.2-r2::gentoo failed (prepare phase):
>  *   Failed Patch: xen-CVE-2013-1442-XSA-62.patch!
>
> and int handle_xsetbv does not appear in 
> xen-4.2.2/xen/arch/x86/xstate.c
>
> Does it really apply to 4.2.x????
>
> --  kind regards
>
> Ian Delaney

It applies to 4.2-stable/staging.  It does however have functional and
textural dependencies on several of the recent backports into that tree,
so if your base tree is not very up to date, you have some extra
backports to do.  (Which is a good thing really, as xsave was
functionally broken before)

~Andrew

  reply	other threads:[~2013-10-02 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 16:47 xen-CVE-2013-1442-XSA-62.patch IAN DELANEY
2013-10-02 16:59 ` Andrew Cooper [this message]
2013-10-02 18:39   ` xen-CVE-2013-1442-XSA-62.patch AL13N
2013-10-02 18:53     ` xen-CVE-2013-1442-XSA-62.patch Andrew Cooper
2013-10-02 19:12       ` xen-CVE-2013-1442-XSA-62.patch AL13N
2013-10-03  9:01         ` xen-CVE-2013-1442-XSA-62.patch Andrew Cooper

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=524C50D9.2010902@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=della5@iinet.com.au \
    --cc=xen-devel@lists.xen.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).