All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Jim Fehlig <jfehlig@suse.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0/4] XEN 4.2 libxl: fix event races exposed by libvirt
Date: Wed, 23 Jan 2013 17:54:36 +0000	[thread overview]
Message-ID: <alpine.DEB.2.02.1301231753460.29727@kaball.uk.xensource.com> (raw)
In-Reply-To: <1358960210-22667-1-git-send-email-ian.jackson@eu.citrix.com>

Jim,
do you have a corresponding libvirt patch that I can try to backport to
0.9.4?

On Wed, 23 Jan 2013, Ian Jackson wrote:
> If we prefix my event race fixes with a couple of backports they apply
> cleanly.
> 
> This is a backport of part of a changeset from unstable, which makes
> the two codebases more textually similar:
>  1/4 libxl: rename "abs" variables to "absolute"
> 
> This is a straightforward cherry pick of a bugfix from unstable:
>  2/4 libxl: Fix passing of application data to timeout_deregister hook
> 
> These are the meat:
>  3/4 libxl: fix stale fd event callback race
>  4/4 libxl: fix stale timeout event callback race
> 

  parent reply	other threads:[~2013-01-23 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 16:56 [PATCH 0/4] XEN 4.2 libxl: fix event races exposed by libvirt Ian Jackson
2013-01-23 16:56 ` [PATCH 1/4] libxl: rename "abs" variables to "absolute" Ian Jackson
2013-01-23 16:56 ` [PATCH 2/4] libxl: Fix passing of application data to timeout_deregister hook Ian Jackson
2013-01-23 22:00   ` Jim Fehlig
2013-01-23 16:56 ` [PATCH 3/4] libxl: fix stale fd event callback race Ian Jackson
2013-01-23 16:56 ` [PATCH 4/4] libxl: fix stale timeout " Ian Jackson
2013-01-23 17:54 ` Stefano Stabellini [this message]
2013-02-22 18:48 ` [PATCH 0/4] XEN 4.2 libxl: fix event races exposed by libvirt Ian Jackson

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=alpine.DEB.2.02.1301231753460.29727@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jfehlig@suse.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 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.