public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: axboe@kernel.dk, linux-kernel@vger.kernel.org
Cc: xen-devel@lists.xensource.com
Subject: One more: Re: [GIT PULL] (xen) stable/for-jens-3.8
Date: Fri, 15 Feb 2013 08:14:06 -0500	[thread overview]
Message-ID: <20130215131406.GA11630@phenom.dumpdata.com> (raw)
In-Reply-To: <20130214232630.GA8440@phenom.dumpdata.com>

On Thu, Feb 14, 2013 at 06:26:30PM -0500, Konrad Rzeszutek Wilk wrote:
> Hey Jens,
> 
> Please git pull the following branch:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-3.8
> 
> which has fixes to the blkback that I hope you can push to Linus for 3.8.
> The one that is quite vicious is the "xen-blkfront: drop the use of
> llist_for_each_entry_safe". It is a fix to re-do an "free-ing" loop - otherwise
> we hit a GCC 4.1.1 bug (so RHEL5 based) that turns the loop in an unbound one.
> 
> Please pull!
> 
>  drivers/block/xen-blkback/blkback.c |  1 -
>  drivers/block/xen-blkback/xenbus.c  | 49 ++++++++++++++++++-------------------
>  drivers/block/xen-blkfront.c        | 13 +++++++---
>  include/linux/llist.h               | 25 -------------------
>  4 files changed, 34 insertions(+), 54 deletions(-)
> 
> Jan Beulich (1):
>       xen-blkback: do not leak mode property
> 
> Konrad Rzeszutek Wilk (2):
>       xen/blkback: Don't trust the handle from the frontend.
>       xen-blkfront: drop the use of llist_for_each_entry_safe
> 

And on the hells of that one, I've got one more ! (yeah, I am sure you
are thrilled about it).

Same branch:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-3.8

This time fixing a memory leak in the xen-blkback with the persistent
grants feature.

 drivers/block/xen-blkback/blkback.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

Roger Pau Monne (1):
      xen-blkback: use balloon pages for persistent grants

Please pull!

If you want to delay pushing them to Linus until 3.9 I can poke Greg
about back-porting those to the stable tree - your call.


      parent reply	other threads:[~2013-02-15 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 23:26 [GIT PULL] (xen) stable/for-jens-3.8 Konrad Rzeszutek Wilk
2013-02-15  9:30 ` Jens Axboe
2013-02-15 13:31   ` Konrad Rzeszutek Wilk
2013-02-15 13:14 ` Konrad Rzeszutek Wilk [this message]

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=20130215131406.GA11630@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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