All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: axboe@kernel.dk, linux-kernel@vger.kernel.org,
	xen-devel@lists.xensource.com
Subject: [GIT PULL] (xen) stable/for-jens-3.14
Date: Mon, 10 Feb 2014 13:44:12 -0500	[thread overview]
Message-ID: <20140210184412.GA18198@phenom.dumpdata.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]

Hey Jens,

Please git pull the following branch:

 git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git stable/for-jens-3.14

which is based off v3.13-rc6. If you would like me to rebase it on
a different branch/tag I would be more than happy to do so.

The patches are all bug-fixes and hopefully can go in 3.14.

They deal with xen-blkback shutdown and cause memory leaks
as well as shutdown races. They should go to stable tree and if you
are OK with I will ask them to backport those fixes.

There is also a fix to xen-blkfront to deal with unexpected state
transition. And lastly a fix to the header where it was using the
__aligned__ unnecessarily.

Please pull!


 drivers/block/xen-blkback/blkback.c | 63 ++++++++++++++++++++++++-------------
 drivers/block/xen-blkback/common.h  |  4 ++-
 drivers/block/xen-blkback/xenbus.c  | 13 ++++++++
 drivers/block/xen-blkfront.c        | 11 ++++---
 include/xen/interface/io/blkif.h    | 34 +++++++++-----------
 5 files changed, 79 insertions(+), 46 deletions(-)

David Vrabel (1):
      xen-blkfront: handle backend CLOSED without CLOSING

Matt Rushton (1):
      xen-blkback: fix memory leak when persistent grants are used

Roger Pau Monne (3):
      xen-blkback: fix memory leaks
      xen-blkback: fix shutdown race
      xen-blkif: drop struct blkif_request_segment_aligned


[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

             reply	other threads:[~2014-02-10 18:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 18:44 Konrad Rzeszutek Wilk [this message]
2014-02-10 19:54 ` [GIT PULL] (xen) stable/for-jens-3.14 Jens Axboe
2014-02-11 15:52   ` [Xen-devel] [GIT PULL] (xen) stable/for-jens-3.14 : NFO: trying to register non-static key. the code is fine but needs lockdep annotation Sander Eikelenboom
2014-02-11 15:52     ` Sander Eikelenboom
2014-02-11 15:56     ` Konrad Rzeszutek Wilk
2014-02-11 16:07       ` Sander Eikelenboom
2014-02-11 16:07         ` Sander Eikelenboom
2014-02-11 17:40         ` Roger Pau Monné
2014-02-11 17:40           ` Roger Pau Monné
2014-02-11 17:52           ` David Vrabel
2014-02-11 17:52             ` David Vrabel
2014-02-11 18:15             ` Roger Pau Monné
2014-02-11 18:15               ` Roger Pau Monné
2014-02-11 18:21               ` David Vrabel
2014-02-11 18:21                 ` David Vrabel
2014-02-11 20:21                 ` Sander Eikelenboom
2014-02-11 20:21                   ` Sander Eikelenboom
2014-02-11 21:44                   ` [Xen-devel] " Jens Axboe
2014-02-12  3:14                     ` Konrad Rzeszutek Wilk
2014-02-12  3:34                       ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2017-06-20 12:13 [GIT PULL] (xen) stable/for-jens-3.14 Konrad Rzeszutek Wilk
2017-06-20 13:11 ` Jens Axboe
2017-06-20 14:18   ` Konrad Rzeszutek Wilk

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=20140210184412.GA18198@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 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.