From: Ian Campbell <ian.campbell@citrix.com>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Jan Beulich" <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.1.x security support
Date: Tue, 17 Sep 2013 20:18:06 +0100 [thread overview]
Message-ID: <1379445486.11304.195.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <52389516.7020905@invisiblethingslab.com>
On Tue, 2013-09-17 at 19:44 +0200, Joanna Rutkowska wrote:
> On 09/17/13 19:38, Joanna Rutkowska wrote:
> > On 09/17/13 08:47, Jan Beulich wrote:
> >>>>> On 17.09.13 at 00:01, Marek Marczykowski-Górecki<marmarek@invisiblethingslab.com> wrote:
> >>> 4.1.6.1 was announced as the last 4.1.x release. Does it mean that further
> >>> XSAs will not carry patches for 4.1?
> >>
> >> That's the way I view it, but that doesn't mean it has to be that way.
> >>
> >
> > That would be rather unfortunate. E.g. we're planning to stick to Xen
> > 4.1 for our Qubes R2 release. There are some problems with Xen 4.2 such
> > as the GPLPV Windows drivers not working with it correctly.
> >
> > I could imagine that it should not be very costly for xen.org to
> > backport each XSA patch to 4.1, should it?
Well, it rather depends on nature of the patch doesn't it. Some are hard
and some are easy.
AFAIK the security team would be happy to receive and distribute
additional backports to older versions done by community members e.g.
those on the predisclosure list.
> And a somehow more general thought: what most people expect from
> baremetal hypervisors, I think, is stability. Unlike the Linux kernel,
> the Xen hypervisor does not need to support each and every device
> invented on the planet, each and every possible filesystem, or
> networking stack, etc. That's, in fact, (one of) the biggest advantage
> of a hypervisor over a monolithic kernel. So, why, oh why, such a race
> to keep bumping the major version over and over again?
What race are you talking about? Do you think we should do something
other than bump the version when we cut a new release? or do you think
we should add features to stable branches or something?
The release cadence has been discussed on the list fairly recently. I
would suggest you make your views known under that topic rather than
here where people might miss it.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-09-17 19:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 22:01 Xen 4.1.x security support Marek Marczykowski-Górecki
2013-09-17 6:47 ` Jan Beulich
2013-09-17 17:38 ` Joanna Rutkowska
2013-09-17 17:44 ` Joanna Rutkowska
2013-09-17 19:18 ` Ian Campbell [this message]
2013-09-17 19:55 ` Joanna Rutkowska
2013-09-17 20:36 ` Marek Marczykowski-Górecki
2013-09-17 20:50 ` Ian Campbell
2013-09-17 20:46 ` Ian Campbell
2013-09-18 10:03 ` Vincent Hanquez
2013-09-18 10:08 ` Joanna Rutkowska
2013-09-18 8:39 ` Jan Beulich
2013-09-18 8:50 ` Joanna Rutkowska
2013-09-18 9:19 ` Sander Eikelenboom
2013-09-18 15:50 ` George Dunlap
2013-09-18 8:33 ` Jan Beulich
2013-09-18 8:37 ` Joanna Rutkowska
2013-09-18 8:50 ` Jan Beulich
[not found] <mailman.9883.1379496660.32487.xen-devel@lists.xen.org>
2013-09-18 13:49 ` Andres Lagar-Cavilla
2013-09-18 15:42 ` George Dunlap
2013-09-19 10:41 ` Pasi Kärkkäinen
2013-09-19 11:23 ` Sander Eikelenboom
2013-09-19 12:09 ` Jan Beulich
2013-09-20 8:12 ` M A Young
2013-09-19 15:55 ` Stefan Bader
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=1379445486.11304.195.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=joanna@invisiblethingslab.com \
--cc=marmarek@invisiblethingslab.com \
--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).