xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Matt Wilson <msw@linux.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
	xen-devel@lists.xensource.com,
	Cristian Gafton <gafton@amazon.com>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [GIT PULL] (xen) stable/for-jens-3.13
Date: Tue, 5 Nov 2013 15:36:46 -0800	[thread overview]
Message-ID: <20131105233646.GA25858@u109add4315675089e695.ant.amazon.com> (raw)
In-Reply-To: <20131105225229.GB21473@u109add4315675089e695.ant.amazon.com>

On Tue, Nov 05, 2013 at 02:52:29PM -0800, Matt Wilson wrote:
> On Tue, Nov 05, 2013 at 11:59:08AM -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.13
> > 
> > 
> > which has a fix to the Xen block frontend driver. For the backends that
> > don't support persistent grants, we don't want to use the logic that would
> > use copying (needed for persistent grants). That logic existed there initially
> > but with the persistent grants code added in - it was removed (so in 3.10
> > time-frame). This adds part of it back.
> 
> I just tested this patch as part of a backported series on top of a
> 3.4.68 base. When this patch is included and a domU boots on a system
> that does not support persistent grants the kernel panics on boot with
> the trace below. Full boot log: http://paste.ubuntu.com/6367329/
> 
> It's possible we missed something in the backport series. I'll test
> this patch on top of 3.11.4 to see how it fares.

Hi Konrad,

Looks like there's something amiss in the backport. Testing your git
branch worked fine.

Sorry for the false alarm.

--msw

      reply	other threads:[~2013-11-05 23:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 16:59 [GIT PULL] (xen) stable/for-jens-3.13 Konrad Rzeszutek Wilk
2013-11-05 17:00 ` Jens Axboe
2013-11-05 17:17   ` Konrad Rzeszutek Wilk
2013-11-05 18:14     ` Jens Axboe
2013-11-05 22:52 ` Matt Wilson
2013-11-05 23:36   ` Matt Wilson [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=20131105233646.GA25858@u109add4315675089e695.ant.amazon.com \
    --to=msw@linux.com \
    --cc=anthony@codemonkey.ws \
    --cc=axboe@kernel.dk \
    --cc=gafton@amazon.com \
    --cc=konrad.wilk@oracle.com \
    --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;
as well as URLs for NNTP newsgroup(s).