All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: axboe@fb.com, linux-kernel@vger.kernel.org,
	xen-devel@lists.xenproject.org
Subject: [GIT PULL] (xen) stable/for-jens-4.2 for rc4
Date: Mon, 27 Jul 2015 13:36:26 -0400	[thread overview]
Message-ID: <20150727173625.GA13387@konrad-lan.dumpdata.com> (raw)

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

Hey Jens,

There are three bugs that have been found in the xen-blkfront (and
backend). Two of them have the stable tree CC-ed. They have been found
where an guest is migrating to a host that is missing 'feature-persistent'
support (from one that has it enabled). We end up hitting an BUG() in the
driver code.

Please git pull the following branch:

git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.2

which has the outlined changes. The branch is based on your
'for-4.2/drivers' branch but it also nicely applies to Linus's tree and
your 'for-linus'.

 drivers/block/xen-blkback/blkback.c |   4 +-
 drivers/block/xen-blkfront.c        | 128 ++++++++++++++++++++----------------
 2 files changed, 74 insertions(+), 58 deletions(-)

Bob Liu (3):
      xen-blkfront: introduce blkfront_gather_backend_features()
      xen-blkfront: don't add indirect pages to list when !feature_persistent
      xen-blkback: replace work_pending with work_busy in purge_persistent_gnt()

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

             reply	other threads:[~2015-07-27 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 17:36 Konrad Rzeszutek Wilk [this message]
2015-07-27 20:58 ` [GIT PULL] (xen) stable/for-jens-4.2 for rc4 Jens Axboe
2015-07-27 20:58 ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2015-07-27 17:36 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=20150727173625.GA13387@konrad-lan.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=axboe@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.