All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Daniel Kiper <daniel.kiper@oracle.com>
Subject: Re: [PATCH] xen/balloon: cancel ballooning if adding new memory failed
Date: Fri, 30 Jan 2015 11:34:02 +0000	[thread overview]
Message-ID: <1422617642.12551.10.camel@citrix.com> (raw)
In-Reply-To: <54CA7580.4090409@citrix.com>

On Thu, 2015-01-29 at 18:01 +0000, David Vrabel wrote:
> On 29/01/15 13:36, Ian Campbell wrote:
> > On Mon, 2014-09-01 at 18:52 +0100, David Vrabel wrote:
> >> If the balloon driver is adding additional memory regions to the
> >> balloon and add_memory() fails it will likely continuously fail so
> >> cancel the balloon operation.
> >>
> >> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776448 and
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001 seem to
> > suggest this should be a candidate for stable backports?
> 
> It's up to the distro kernel maintainer to request it if they think it
> is important.

Which is what I thought I was doing. Surely you don't think I should
just ask stable@ without conferring with the relevant maintainers first?

Ian.

  parent reply	other threads:[~2015-01-30 11:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 17:52 [PATCH] xen/balloon: cancel ballooning if adding new memory failed David Vrabel
2014-09-01 22:07 ` Daniel Kiper
2014-09-02 17:23   ` David Vrabel
2015-01-29 13:36 ` Ian Campbell
2015-01-29 18:01   ` David Vrabel
2015-01-29 20:35     ` Daniel Kiper
2015-01-30 11:34     ` Ian Campbell [this message]
2015-01-30 11:53       ` David Vrabel
2015-01-30 12:03         ` Ian Campbell

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=1422617642.12551.10.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=daniel.kiper@oracle.com \
    --cc=david.vrabel@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.