From: Daniel Stodden <daniel.stodden@citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
tsk <aixt2006@gmail.com>
Subject: Re: blktap2 bug:Assertion 'list_empty(&vreq->next)' failed
Date: Mon, 5 Jul 2010 16:25:24 -0700 [thread overview]
Message-ID: <1278372324.375.7172.camel@agari.van.xensource.com> (raw)
In-Reply-To: <4C325BFD.4020405@goop.org>
On Mon, 2010-07-05 at 18:26 -0400, Jeremy Fitzhardinge wrote:
> On 07/05/2010 02:25 PM, Daniel Stodden wrote:
> > On Thu, 2010-07-01 at 08:55 -0400, tsk wrote:
> >
> >> Hi, will the patches be added to Xen-4.1?
> >>
> > About to prepare the next bunch of patches for xen.git.
> >
> > Jeremy, is it okay to pull some of the changes made for 2.6.3x into the
> > xen/dom0/backend/blktap2 topic branch before moving on?
> >
> > I'm mainly talking about this one:
> >
> > >From ab77527f9a63a5c657c6d6a50e70a66adceaa3a0 Mon Sep 17 00:00:00 2001
> > From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > Date: Thu, 18 Feb 2010 17:22:09 -0800
> > Subject: [PATCH] xen/blktap2: make compile
> >
> > and a couple related deltas which came later.
> >
> > Except moving forward to newer blk queue interfaces, they don't make
> > much of a functional difference.
> >
> > Would simplify merging quite a bit.
> >
>
> Which kernel version has these interface updates? Do they predate the
> version the blktap2 branch is rooted on, or do the come later? If
> they're later, then merge the mainline kernel (ideally a tagged release
> like v2.6.3[12]) into the blktap2 one and cherrypick the "make compile"
> changes on top of the merge (and if they're already there, then just
> cherrypick).
Okay, the HG follower in me didn't quite follow yet the cherry-related
part of that procedure. But altogether it sounds quite promising.
Followup later. Thanks! :)
Daniel
prev parent reply other threads:[~2010-07-05 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 4:41 blktap2 bug:Assertion 'list_empty(&vreq->next)' failed tsk
2010-06-28 4:48 ` tsk
2010-06-28 4:49 ` [Xen-devel] " Daniel Stodden
2010-06-28 4:58 ` tsk
[not found] ` <1277701807.9747.1905.camel@ramone.somacoma.net>
[not found] ` <AANLkTikcN8oX-LG8bhsa8CQJTjn1CLFvNuwkThMSb5yR@mail.gmail.com>
2010-07-05 21:25 ` Daniel Stodden
2010-07-05 22:26 ` Jeremy Fitzhardinge
2010-07-05 23:25 ` Daniel Stodden [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=1278372324.375.7172.camel@agari.van.xensource.com \
--to=daniel.stodden@citrix.com \
--cc=aixt2006@gmail.com \
--cc=jeremy@goop.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.