All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: "lars.kurth@xen.org" <lars.kurth@xen.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: preparing for 4.3.2 and 4.2.4
Date: Mon, 13 Jan 2014 13:33:25 -0500	[thread overview]
Message-ID: <52D43175.3030904@terremark.com> (raw)
In-Reply-To: <52D410E102000078001132F8@nat28.tlf.novell.com>

On 01/13/14 10:14, Jan Beulich wrote:
> Aiming at a release in late January or early February, I'd like to cut
> RC1s later this or early next week.
>
> Please indicate any bug fixes that so far may have been missed
> in the backports already done.
>
> Thanks, Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


I do not see:


commit 3dbab7a8bf4bef1bb2967cb3a8c7ed2146482ab3


in any 4.2 or 4.3 tree.  As Andrew Cooper said:


 > This is a hypervisor reference counting error on a toolstack hypercall
 > path.  Irrespective of any of the other patches in this series, I think
 > this should be included ASAP (although probably subject to review from a
 > third person), which will fix the hypervisor crashes from gdbsx usage.

    -Don Slutz

  parent reply	other threads:[~2014-01-13 19:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 15:14 preparing for 4.3.2 and 4.2.4 Jan Beulich
2014-01-13 15:31 ` Andrew Cooper
2014-01-17 15:43   ` Jan Beulich
2014-01-13 16:49 ` Ian Jackson
2014-01-13 16:57   ` Ian Campbell
2014-01-13 18:33 ` Don Slutz [this message]
2014-01-13 18:38 ` Don Slutz
2014-01-14  7:49   ` 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=52D43175.3030904@terremark.com \
    --to=dslutz@verizon.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=lars.kurth@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --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.